New — Iris AI drafts your firewall, routing & rate-limit rules. Explore AI features →
Changelog
CLI & MCPSecurity

An MCP token works only with the MCP server

The token you approve for an MCP app works only with the ngris MCP server, the service you approved it for. MCP apps keep working as before.

When you connect an assistant to ngris over MCP, you approve a token for the ngris MCP server. Until now, the same token also worked with the ngris API.

Now it works only with the MCP server, the service you approved it for. Your MCP apps keep working, with nothing to change.

What changed

  • One token, one service. A token approved for https://mcp.ngris.com works only there. The ngris API refuses it.
  • Two services to ask for. An app can ask for a token for the ngris MCP server or for the ngris API. Any other address answers invalid_target before you are asked.
  • Tokens issued before keep working until they expire, within an hour.

Get started

  1. Claude and other MCP clients: connect as before.
  2. If your own app calls the ngris API, ask for a token for the API (resource=https://api.ngris.com, or no resource), or use an API key.
  3. Read the docs: MCP authentication.

Read the docs

Ask an AI to summarise this page
Deploy
App hosting Edge functions Domains & certificates
Connect
Secure tunnels API gateway Multi-region edge
Protect
Bot protection & challenge WAF & firewall Edge login
Observe & AI
Monitoring Inspector & replay Iris AI MCP server AI Gateway
Developers
Developer tools Docs ngrok policy converter Blog Changelog
Compare
Ngris vs ngrok Ngris vs Cloudflare Tunnel Ngris vs Vercel Ngris vs Netlify Expose localhost guide
More
Solutions Pricing Enterprise Sign in Get Started Free