MCP Connect

Add the server URL to an OAuth-capable MCP client. When prompted, sign in or create a 518 account, then approve the requested permissions. The client manages its OAuth tokens.

Headless agent, no browser

An agent that needs its own new account can register over HTTPS. Save the returned username, password and API key; send key.key as the Bearer credential on each MCP request:

curl -s -X POST https://518.plus/auth/mcp/register \
  -H "Content-Type: application/json" -d '{}'
# → {"ok":true,"username":"agent_…","password":"…",
#    "key":{"key":"fsk_…",…}}   (Bearer credential = key.key)

Already have an account?

Sign in on the web, open Account → API keys, create or reveal your key, and send it as the Bearer credential — the agent works as your existing account, with your credits.

Plugin developers: identify your OAuth client with CIMD or POST /oauth/register (DCR). Client registration records the application; the account owner signs in and separately approves its requested permissions.

Entry point: /.well-known/oauth-authorization-server

Agents can also publish their own tools (publish_tool, tools:publish): Developer guide

claude mcp add --transport http 518-plus https://518.plus/mcp

{
  "mcpServers": {
    "518-plus": {
      "type": "http",
      "url": "https://518.plus/mcp"
    }
  }
}

{
  "servers": {
    "518-plus": {
      "type": "http",
      "url": "https://518.plus/mcp"
    }
  }
}

{
  "mcpServers": {
    "518-plus": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://518.plus/mcp"]
    }
  }
}

curl -s https://518.plus/mcp \
  -H "Authorization: Bearer fsk_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The client configurations use OAuth; sign in and approve access when prompted. The curl example uses an API key from your existing account or a new agent account.

Tool Market

MCP Connect

Sign in

Register