Skip to main content
Dedicated Client IDs exist for: For any other MCP-compatible client (for example Cursor), use the generic Client ID below — if the client supports remote MCP (Streamable HTTP) and OAuth. Client UI labels vary.

​
Values to enter

​
Typical flow

  1. Add a remote / custom MCP server in your client.
  2. Paste the Tyms URL for the access level you want.
  3. If asked for a Client ID, enter usetyms-mcp-client.
  4. Complete Tyms OAuth and approve a business.
  5. Enable the server / tools for the session, then ask questions.
If a client only supports local stdio MCP servers (and not remote HTTPS + OAuth), it will not work with Tyms MCP as documented here. Tyms MCP is a hosted remote server — there is no local package to install.

​
If something looks wrong

  • You only see list/get tools → you are on the read-only URL; switch to /full for write tools. See FAQ.
  • Auth fails on Client ID → confirm you used usetyms-mcp-client for unknown clients (or the platform-specific ID if you are on Claude, ChatGPT, or Perplexity).
  • Wrong business data → reconnect and approve the correct business during OAuth.