The TEC-CoWork MCP server (TEC-CoWork Connect) enables Cursor to use the TEC-CoWork capabilities your organization has made available to you: Gmail read/search, Calendar list/create, Drive search/read, Gmail draft creation, shared MCP connections such as Notion, Linear, Slack, Stripe, Exa, and Context7, shared skills, and TEC-CoWork Cloud resources like skills, plugins, marketplaces, workers, members, roles, teams, and LLM providers. The server exposes only search_capabilities and execute_capability, so Cursor searches what you can access and runs exact capability names instead of loading hundreds of tool definitions into context.

​
Server URL

OAuth sign-in uses your TEC-CoWork account, and the organization you pick is pinned into the token. If you do not have an account, create a free TEC-CoWork account.

​
Cursor Desktop

Add TEC-CoWork as a remote MCP server in Cursor’s MCP settings, paste the server URL, and start OAuth from Cursor’s connection prompt. Sign in to TEC-CoWork and pick the organization Cursor should use. Cursor Desktop’s OAuth callback is the private-use URI cursor://anysphere.cursor-mcp/oauth/callback. TEC-CoWork accepts exactly this callback through an allowlist and enforces PKCE S256 for the client, so an intercepted authorization code cannot be redeemed without the code verifier. Other private-use callback schemes remain rejected: TEC-CoWork otherwise accepts HTTPS callbacks or HTTP loopback callbacks only.

​
Cursor Web and Cursor Agents

Use Cursor Web or Cursor Agents where they ask for a remote MCP server URL. Paste the server URL, start OAuth from Cursor’s connection prompt, sign in to TEC-CoWork, and pick the organization Cursor should use. Cursor Web and Cursor Agents use HTTPS OAuth callbacks, which TEC-CoWork accepts.

​
Switch organizations

Remove the stored MCP auth token for tec-cowork, then connect again and choose the organization you want during browser sign-in.
This is a setup guide for Cursor Desktop, Cursor Web, and Cursor Agents. These steps match TEC-CoWork Connect’s OAuth profile: HTTPS or HTTP loopback callbacks plus Cursor Desktop’s allowlisted private-use callback, PKCE S256, and dynamic client registration fallback. Cursor is listed as setup only because native proof is not complete. See the client support status table.

​
What you can ask

  • “Which TEC-CoWork organization am I connected to?”
  • “Add omar@example.com to my organization.”
  • “Search my org’s capabilities for calendar tools, then list tomorrow’s events.”
  • “Find the Q3 launch page in Notion and summarize it.”

​
What’s next

  • Read the hub overview for OAuth, token, server exposure, and troubleshooting details.
  • Publish Notion, Linear, Slack, and other shared tools with shared MCP connections.