Skip to content
Open app

Connect your agent

Cursor

Cursor MCP config
Add to .cursor/mcp.json
{ "mcpServers": { "skillist-registry": { "url": "https://api.skillist.io/mcp" } } }

Restart Cursor or reload MCP servers. OAuth-capable Cursor builds discover authorization automatically — see OAuth authentication.

Ask your agent to call registry_facets or registry_search with query "performance". You should see public skills from the skillist org.

Use the remote HTTP transport with the same URL in your MCP config. Consult Anthropic’s MCP docs for the config file location on your OS.

If your VS Code MCP extension supports streamable HTTP, point it at https://api.skillist.io/mcp via the extension’s server registration UI or settings.json.

The server is stateless (MCP 2026-07-28): every request is its own POST — no initialize handshake, no session header. Requests carry the protocol version and client info in params._meta, mirrored into the MCP-Protocol-Version and Mcp-Method headers (plus Mcp-Name on tools/call):

Terminal window
curl -s https://api.skillist.io/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "MCP-Protocol-Version: 2026-07-28" \
-H "Mcp-Method: tools/list" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {
"_meta": {
"io.modelcontextprotocol/protocolVersion": "2026-07-28",
"io.modelcontextprotocol/clientInfo": { "name": "curl", "version": "1.0.0" },
"io.modelcontextprotocol/clientCapabilities": {}
}
}
}'

Clients on 2025-era protocol revisions can still open with initialize — the handshake is answered from the same tools, per request, with no session minted.

The skillist/registry-mcp skill documents registry MCP usage for agents. Install it with:

Terminal window
skillist install skillist/registry-mcp

Troubleshooting

IssueFix
401 from MCP clientComplete OAuth sign-in at console.skillist.io/login if your client requires tokens
405 on GET or DELETESessions were removed (MCP 2026-07-28) — send each message as its own POST
400 HeaderMismatch (-32020)MCP-Protocol-Version / Mcp-Method / Mcp-Name headers must match the request body
CORS errorsEnsure your client sends Content-Type: application/json
OAuth discovery failsConfirm /.well-known/oauth-protected-resource is reachable — see OAuth docs