Developer Guides

Plugsky MCP server: setup, tools and OAuth 2.1 in one guide

Plugsky MCP connects any Model Context Protocol client — ChatGPT Connectors, Claude, Cursor, VS Code, Windsurf, Zed — to 36+ AI models, web search, memory, browsing, code execution and your knowledge base over one connection. This guide covers the remote URL setup, the npm install for local clients, the 20 live tools, OAuth 2.1 with dynamic client registration, prompts and resources.

Key facts

Remote endpointhttps://plugsky.com/mcp (Streamable-HTTP, Bearer auth)
Local installnpx -y @plugsky/mcp (stdio; --groups to narrow tools)
AuthAPI key or OAuth 2.1 + Dynamic Client Registration with PKCE
Tools20 live: chat, models, fusion, web search/fetch, transcripts, audio, vision, image, memory, RAG fusion, browse, code, ingest
Prompts / Resources12 prompts + 10 resources (MCP spec primitives)
Clients supportedChatGPT, Claude Desktop, Cursor, VS Code, Windsurf, Zed, Cline, Continue, LM Studio, OpenWebUI
Reliability7-tier model failover behind plugsky_chat; per-tool usage metering; scoped keys enforced

TL;DR

  • Remote setup is a URL plus your API key — no install.
  • Local clients use npx -y @plugsky/mcp.
  • OAuth 2.1 + DCR supported for connectors that require it.
  • 20 tools cover search, transcripts, audio, vision, image, memory, browsing, code and RAG.
  • Free tier available for evaluation; paid plans are fair-use.

Remote setup, step by step

  1. Create an API key in Dashboard → API Keys.
  2. In your MCP client, add a remote server named plugsky with URL https://plugsky.com/mcp and header Authorization: Bearer YOUR_KEY.
  3. Run the client's tool discovery — you should see 20 tools, 12 prompts and 10 resources.
  4. Ask the model to call plugsky_models to confirm the connection.

OAuth 2.1 and dynamic client registration

Connectors that require OAuth discover the authorization server at /.well-known/oauth-authorization-server, register dynamically at POST /oauth/register, then complete a PKCE authorization-code flow. Tokens are regular Plugsky API keys, scoped to mcp.read, mcp.write or full mcp access — enforced per tool.

What the 20 tools cover

Chat with 36+ model aliases behind a 7-tier provider failover; search the web (single and fused multi-engine); fetch or ground pages; pull YouTube and video captions; transcribe audio with Whisper; describe screens and generate images with FLUX; save and search persistent memory; fuse your knowledge store; browse JS-heavy pages with headless Chromium and persistent sessions; run sandboxed Python; and ingest sites into memory.

Frequently asked questions

Is Plugsky MCP free to try?

Yes — the free plan includes two models and 500 requests/day; a 14-day trial unlocks everything.

Does it work in ChatGPT?

Yes, via Connectors with developer mode: add https://plugsky.com/mcp and your key (OAuth supported for Business/Enterprise).

Can I limit which tools a key can use?

Yes. OAuth-scoped keys (mcp.read / mcp.write) are enforced per tool; local installs can narrow groups with --groups.

Where is usage metered?

Every tool call is metered per user — see Dashboard → Usage & Analytics.

Cite this page

Plugsky (2026). “Plugsky MCP Server: Setup, Tools and OAuth 2.1 Guide”. Plugsky. Available at: https://plugsky.com/articles/plugsky-mcp-server-guide (last updated 2026-09-30).