MCP Pillar Resource Hub

MCP Server Development

How to build, test, and deploy MCP servers.

Quick Answer / TL;DR

Python, TypeScript, and .NET SDKs are available for building MCP servers. MCP Archetypes demonstrates implementations using different frameworks, transports, and authorization methods.

Key Takeaways

  • Standardized JSON-RPC 2.0 communication format
  • Compatible with Claude Desktop, Cursor, and other MCP-speaking clients
  • Replaces one-off API integrations with a single client-server interface
Key Compliance Rule: Under the DPDP Act 2023, MCP servers processing Indian user data must enforce data localization and maintain immutable audit logs.

2. How It Works

The project shows how to define tools (@tool) that can be consumed by LLMs. ServiceNow MCP server uses Server-Sent Events (SSE) for communication.

1

Client Discovery

Client queries the local/remote MCP server capabilities via standard JSON-RPC handshake.

2

Schema Mapping

Exposed resources, tools, and templates are dynamically validated against standardized schemas.

3. When to Use It

This standard protocol should be implemented whenever an application requires:

  • Real-time database queries prompted dynamically by user conversations.
  • Secure interaction with private enterprise repositories (GitHub, GitLab).
  • Dynamic tool call structures that avoid hardcoded server routes.

4. Connection Architecture

Standard Protocol Stack Flow

  1. Transport Protocol: Configurable Stdio pipeline or Server-Sent Events (SSE).
  2. RPC Layer: 100% compliant JSON-RPC 2.0 message parsing.
  3. Validation Layer: Strict JSON-Schema constraints check for error-free queries.

5. Standard Setup Instructions

# Install the official MCP SDK

npm install @modelcontextprotocol/sdk

# Configure server inside Claude Desktop config

{ "mcpServers": { "my-server": { "command": "node", "args": ["dist/index.js"] } } }

6. Security & Isolation Controls

Because MCP servers run locally or inside hosted cloud environments, they have direct code execution abilities. Always constrain environments, rotate keys, use secure SSE paths, and authorize write operations.

7. Engineering Best Practices

Keep Schemas Minimal

Avoid deeply nested structures so LLMs can map parameters accurately.

Stderr Logging

Always log debugging outputs to stderr, keeping stdout clean for JSON-RPC messages.

Common Configuration PitfallHardcoding private API keys inside the server configuration blocks. Instead, pass credentials dynamically via system environment variables.

In Practice

What the SDKs Actually Handle for You

The official Python and TypeScript SDKs handle the JSON-RPC framing, the initialize handshake, and request/response routing — what's left to the developer is defining tool schemas and writing the handler logic. Getting the schema right is most of the real work; a vague or overly permissive schema is the most common source of a model misusing a tool.

A practical development loop: write the tool, test it manually against the schema with a minimal script before wiring it into a real client, then verify the client actually surfaces the tool correctly — client-side rendering of tool descriptions has historically been where subtle bugs hide.

Supported Integrations

M
MCPserver.in Engineering

Platform Team

Published: 2026-07-19
Updated: 2026-07-19

Deploy Node Globally

Deploy ultra-low latency Model Context Protocol nodes to Mumbai / Bengaluru edge clusters with zero DevOps management.

Start Managed Hosting

Platform Features

  • Standard JSON-RPC handshake
  • Secure isolated Sandbox

MCP Server Development - FAQs

Contextual information and technical support details regarding Model Context Protocol integration

Recommended Reading & Resources