Cursor, VS Code, Codex, and other MCP clients + Specky
Connect Specky to Cursor, VS Code, Codex, and MCP Clients
Compatible MCP clients can connect to Specky with one Streamable HTTP URL: https://www.specky.space/api/mcp. Use OAuth when the client supports browser authorization, or a workspace-scoped key for headless automation.
Canonical MCP endpoint
https://www.specky.space/api/mcpStreamable HTTP · OAuth 2.1 with PKCE · workspace key fallback
Setup
Connect Cursor, VS Code, Codex, and other MCP clients to Specky
Follow the provider-specific path below. The exact menu names and availability can change as each provider evolves its MCP and directory programs.
- 01
Add a remote HTTP MCP server
Create a client entry named specky and set its URL to https://www.specky.space/api/mcp. The exact configuration key varies by client.
- 02
Authorize the intended workspace
Use the client’s browser OAuth flow where available. For headless clients, send Authorization: Bearer sk_live_… with a workspace-scoped Specky key.
- 03
Run a read-first smoke test
List tools, search one product question, and read one returned item. Check citations and workspace boundaries before enabling writes.
{
"mcpServers": {
"specky": {
"url": "https://www.specky.space/api/mcp"
}
}
}Use provider-managed secrets or OAuth for authenticated workspaces. Do not paste a workspace key into public client-side code.
What to test first
Use one bounded, read-first prompt so you can inspect the returned evidence and confirm the workspace boundary:
Find the strongest evidence behind this customer problem, show the sources and unknowns, and draft a problem statement. Do not create tickets or change records until I approve the draft.
Questions about Specky and Cursor, VS Code, Codex, and other MCP clients
Which clients can use Specky’s MCP endpoint?+
Cursor, VS Code, Codex, Claude Code, n8n, and other clients that support Streamable HTTP MCP can use the same endpoint, subject to each client’s authentication support.
Do I need a marketplace listing to use Specky in Cursor?+
No. A compatible MCP client can connect directly to the endpoint. Marketplace listings are discovery channels, not a prerequisite for a private or team connection.
What should a developer verify before enabling writes?+
Verify the workspace identity, tool descriptions, input schemas, approval expectations, and returned citations. Keep the initial client configuration read-only where possible.