MCP Server JSON Spec
MCP Server JSON Spec
Configure your AI clients to use your Rapid MCP server
Overview
Use this guide to connect agents to your Rapid MCP server via Stream (recommended) or SSE. Headers can be templated and automatically applied to tool calls.
Stream (URL)
The following JSON config works for clients that accept an MCP URL.
{
"mcpServers": {
"RapidMCP": {
"url": "https://rapid-mcp.com/mcp/<serverId>/stream",
"headers": {
"Authorization": "Bearer XXXXX"
}
}
}
}Notes:
- "headers" are automatically passed to every tool call.
Stream (npx)
For clients that use command-based connectors:
{
"mcpServers": {
"RapidMCP": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://rapid-mcp.com/mcp/<serverId>/stream",
"--header",
"api-key:${AUTH_HEADER}",
"--header",
"subdomain:${SUBDOMAIN}"
],
"env": {
"AUTH_HEADER": "Bearer XXXXXXX",
"SUBDOMAIN": "subdomain-v1-example"
}
}
}
}Tip: api-key must be lowercase and contain no spaces so it maps to {{api-key}} in tool templates.