Skip to content
MaskioEU

Reverse Proxy MCP Gateway · JSON-RPC

Give agents live CRM tools. Never give them real PII or credentials.

Maskio sits between MCP clients and the servers you already run. Tool reads are masked. Tool writes are restored in flight. A read-only policy can refuse destructive calls before they reach Postgres.

Streamable HTTP · Claude Desktop · Cursor · Windsurf · n8n

  1. 01

    Agent calls get_customer through mcp.maskio.io.

  2. 02

    The CRM row is tokenized in RAM before the model sees it.

  3. 03

    update_deal comes back with [EMAIL_1] and is restored at the edge.

  4. 04

    delete_contact or DROP TABLE stops when the policy says so.

Authentication is not privacy. Redaction is not agent-compatible.

Ordinary MCP routers

They terminate OAuth and rate limits, then forward the raw customer record into the model once the call is allowed.

One-way redaction

Stars and [REDACTED] blocks remove the identifier the next tool needs. The invoice or CRM update fails.

Maskio

[PERSON_1] and [IBAN_1] stay stable for the session and are resolved only on the upstream hop.

Paste a tool payload.

This inspector runs locally. The production gateway applies the same idea on the EU cluster with your real upstream.

Policy

ALLOWED · 11.4ms

What the model receives

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "get_customer",
    "arguments": { "email": "[EMAIL_1]", "nif": "[NIF_1]" }
  }
}

Wrap a server in three steps.

  1. 01 Register the real MCP URL and its auth header in the workspace. The header is encrypted at rest.
  2. 02 Copy the gateway URL. Production form: https://mcp.maskio.io/v1/mcp/gateway/{id}.
  3. 03 Paste it into Claude Desktop or Cursor with a Bearer mp_live_ key that includes the proxy:mcp scope.
{
  "mcpServers": {
    "crm-protected": {
      "url": "https://mcp.maskio.io/v1/mcp/gateway/gw_live_98a7f6",
      "headers": { "Authorization": "Bearer mp_live_..." }
    }
  }
}

Questions

Which MCP transports work?+

The gateway accepts Streamable HTTP (POST, GET, and DELETE) on /v1/mcp/gateway/{id}. The native server also exposes legacy SSE at /v1/mcp/sse for older clients.

How long do tokens last?+

The dictionary stays in RAM for the workspace TTL: 15 minutes on Free, 1 hour on Builder, 24 hours on Team, and up to 7 days for MCP tokens on Agency.

Can one workspace front several MCP servers?+

Yes. Register each upstream separately. Tokens are scoped to the workspace, so a person token from Postgres can be restored on a later HubSpot call in the same session.

Put the airlock in front of the servers you already trust.

The free plan includes 1,000 bidirectional MCP calls a month.