Any MCP client

Nimply's MCP server is a standard remote server. Any client that implements the MCP spec can connect — including ones that don't exist yet.

The three connection shapes

1. OAuth-capable clients (connector-style UIs): just give them the URL —

https://mcp.nimply.io/mcp

The server advertises its authorization server via RFC 9728 protected-resource metadata; the client discovers it, registers itself, and walks you through Nimply's consent screen. Nothing to copy.

2. Header-capable clients (config-file tools): same URL plus one header —

Authorization: Bearer nim_live_YOUR_KEY

Create the key in Nimply → Settings → Developers.

3. Stdio-only clients (no remote support): bridge with mcp-remote:

npx -y mcp-remote https://mcp.nimply.io/mcp \
  --header "Authorization: Bearer nim_live_YOUR_KEY"

Configure that command wherever the client expects a local MCP server. Without the --header, mcp-remote runs Nimply's OAuth flow in your browser instead.

Verify from the terminal

curl -s https://mcp.nimply.io/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer nim_live_YOUR_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

A tool list means auth and transport are fine — any remaining trouble is client configuration.

Details

• Transport: Streamable HTTP (MCP spec 2025-06-18); no SSE-only legacy endpoint.
• Tools: listed in the MCP overview.
• Rate limits and permissions are those of the credential — see Authentication.