​
Overview

The Jmpy.me MCP server is hosted at https://jmpy.me/mcp and follows the Model Context Protocol (MCP) specification. You can connect any MCP-compatible client to interact with your Jmpy.me account.

​
Prerequisites

  • An active Jmpy.me account
  • MCP API key from API Key Settings
  • An MCP-compatible client (Claude Desktop, n8n, etc.)

​
Getting Your MCP API Key

1

Sign In

Log in to your Jmpy.me account at app.jmpy.me/login
2

Access Developer Settings

Navigate to Dashboard → API Keys or go to app.jmpy.me/dashboard/api-keys
3

Create MCP API Key

Click Create New API Key and select MCP permissions
4

Copy Your Key

Copy the API key starting with jmpy_ - you’ll need it for configuration

​
Configuration

The Jmpy.me MCP server supports multiple connection methods to ensure compatibility with all AI assistants and automation tools. Choose the configuration that matches your client.

​
1. AI Assistants (Using JSON Config)

Many modern AI assistants and IDE extensions use a config.json file for MCP server management. 
{
  "mcpServers": {
    "jmpy": {
      "command": "node",
      "args": [
        "-e",
        "const http = require('https'); const options = { hostname: 'jmpy.me', port: 443, path: '/mcp', method: 'POST', headers: { 'Content-Type': 'application/json', 'x-mcp-key': process.env.JMPY_API_KEY } }; const req = http.request(options, (res) => { res.pipe(process.stdout); }); process.stdin.pipe(req);"
      ],
      "env": {
        "JMPY_API_KEY": "your_mcp_api_key_here"
      }
    }
  }
}
Pro Tip: If your client gives an error like serverURL or command must be specified, ensure you are using the serverURL property name instead of url.

​
2. Automation Tools (n8n, Make, Zapier)

For workflow automation, use the standard HTTP or SSE transport provided by the tool.

n8n Integration

  1. Add an MCP Node
  2. Set URL to https://jmpy.me/mcp
  3. Add header x-mcp-key

Custom Webhooks

  1. Use POST https://jmpy.me/mcp
  2. Send JSON-RPC 2.0 payload
  3. Header: x-mcp-key

​
3. Connection Property Reference

If you are building your own client or using a custom app, refer to these property mappings to handle different SDK implementations:
RequirementProperty NameValue / Endpoint
SSE Connection URLserverURL or urlhttps://jmpy.me/mcp/sse
HTTP API EndpointbaseUrl or pathhttps://jmpy.me/mcp
Transport Typetypesse or stdio (via wrapper)
Authentication Headerheadersx-mcp-key: jmpy_...
Env VariableenvJMPY_API_KEY

​
4. Direct HTTP API (Manual Exploration)

You can interact with the MCP server directly via raw HTTP requests for testing: You can also interact with the MCP server directly via HTTP: 
# Initialize connection
curl -X POST https://jmpy.me/mcp \
  -H "Content-Type: application/json" \
  -H "x-mcp-key: YOUR_MCP_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "clientInfo": {
        "name": "my-client",
        "version": "1.0.0"
      }
    }
  }'

​
MCP Endpoints

EndpointMethodDescription
/mcpPOSTMain JSON-RPC 2.0 protocol endpoint
/mcpGETServer identification and info
/mcp/toolsGETList available tools
/mcp/resourcesGETList available resources
/mcp/promptsGETList available prompts
/mcp/healthGETServer health check

​
Authentication

The MCP server uses the x-mcp-key header for authentication: 
x-mcp-key: jmpy_your_api_key_here
MCP API keys have specific rate limits based on your subscription plan. Check your API Key Settings for current limits.

​
Verification

After configuration, verify the connection:

​
1. Check Server Status

curl https://jmpy.me/mcp
Should return server information: 
{
  "name": "jmpy-mcp-server",
  "version": "1.1.0",
  "protocolVersion": "2024-11-05"
}

​
2. List Available Tools

curl -X GET https://jmpy.me/mcp/tools \
  -H "x-mcp-key: YOUR_MCP_API_KEY"

​
3. Test a Simple Command

curl -X POST https://jmpy.me/mcp \
  -H "Content-Type: application/json" \
  -H "x-mcp-key: YOUR_MCP_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'

​
Troubleshooting

  • Verify your API key is correct and starts with jmpy_
  • Ensure you’re using the x-mcp-key header (not Authorization)
  • Check that your API key hasn’t been revoked
  • Your plan may not include MCP access
  • Check your plan limits in Developer Settings
  • Upgrade to Pro or Enterprise for MCP access
  • MCP operations are rate-limited per your plan
  • Wait for the rate limit window to reset
  • Consider upgrading for higher limits
  • Verify network connectivity to jmpy.me
  • Check if your firewall allows HTTPS connections
  • Try the health endpoint: https://jmpy.me/mcp/health

Available Tools

View the complete list of MCP tools

Resources

Learn about MCP resources