Connect Cursor, VS Code (Copilot) and other MCP clients
Any client that supports remote (HTTP) MCP servers can connect. It signs in with OAuth if it supports it; otherwise create an API access key and send it as a bearer token.
Two ways to authenticate
| Method | When to use it | How |
|---|---|---|
| OAuth 2.1 with PKCE | Clients with built-in MCP sign-in | Add the URL; the client registers itself and opens the browser for you to sign in and allow access. |
| API access key | Clients that take a header, scripts, or clients whose sign-in returns through a custom app link | Dashboard → MCP tools → create an access key with the lowest role that works (it is shown once), then send Authorization: Bearer <key>. |
Cursor
Add the server to ~/.cursor/mcp.json (or the project's .cursor/mcp.json):
{
"mcpServers": {
"wecommander": {
"url": "https://wecommander.app/mcp",
"headers": { "Authorization": "Bearer <your API access key>" }
}
}
}VS Code with GitHub Copilot
Add an HTTP server in .vscode/mcp.json (or with the MCP: Add Server command). VS Code signs in with OAuth when the server asks for it; to use an API access key instead, add "headers": { "Authorization": "Bearer <your API access key>" } next to the url.
{
"servers": {
"wecommander": {
"type": "http",
"url": "https://wecommander.app/mcp"
}
}
}Any other client or a script
The endpoint speaks MCP JSON-RPC over HTTP POST (protocol versions 2025-06-18 and 2025-03-26): initialize, notifications/initialized, ping, tools/list and tools/call.
curl -s https://wecommander.app/mcp \
-H "Authorization: Bearer $WECOMMANDER_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Keep keys safe
- A key acts with the role you gave it: viewer reads, operator runs tools (high-risk ones still need approval), admin and owner manage more. Use the lowest that works.
- Never commit a key to a repository or a shared file. Revoke it on the MCP tools page when it is no longer needed.
- An AI client or API key can never approve its own requests or change AI permissions.
- AI access with MCP: how it works: What MCP (Model Context Protocol) is, the one WECOMMANDER MCP URL (https://wecommander.app/mcp), how a tool call reaches your machine, and the two ways to connect a server: the agent or SSH.
- Local MCP: without an account or through the desktop app: Run WECOMMANDER as a local MCP server over stdio for Claude Desktop, Cursor, VS Code or Codex: the agent's mcp-stdio mode with no account, or the Windows app's local endpoint for saved SSH servers.
- Workspaces, teams, roles and API keys: Workspaces, the owner, admin, operator and viewer roles, inviting members, API access keys for MCP clients, and the workspace region.