Connect AI Apps with MCP

What the MCP Connector Is

Thicket runs a remote MCP (Model Context Protocol) connector, so AI apps that speak MCP can work inside your projects: list to-dos and check them off, post messages and comments, read docs, move board cards, follow the schedule, and search. It works with compatible remote MCP clients and uses the same permissions your own account has.

The connector URL is:

https://www.thickethq.com/api/mcp

Connecting

1. In your MCP client, add a remote server (sometimes called a connector or integration) and paste the URL above
2. The client opens Thicket in your browser. Sign in if you aren't already
3. A consent screen names the app and lists exactly what it will be able to do. Click Allow to connect, or Deny to send it away

That's the whole setup. There is no token to copy for OAuth clients, and the client never sees your password.

What a Connected App Can Do

• It works as you: the same organizations, the same projects, the same role. A client-role account connected over MCP still sees only what the team shares
• Every action it takes is attributed to you in the project timeline, like anything you do yourself
• Read-only connections exist: if the app asks only for read access, the consent screen says so, and it never sees the write tools at all
• It cannot delete anything, manage people or billing, change settings, or download files. Those tools are deliberately not part of the connector

Disconnecting

Open My settings → Connected apps. Every connection shows the app's name, its access (read-only or read and write), when it was connected, and when it was last used. Click Disconnect and access ends immediately; the app's tokens stop working on its very next request.

Using a Personal Access Token Instead

Some tools (scripts, the MCP Inspector, clients that support custom headers) prefer a token to a browser sign-in. Create one under My settings → API tokens and send it to the same URL as Authorization: Bearer thicket_pat_... with a User-Agent header. A read-only token sees only the read tools. Revoke it from the same page.

Troubleshooting

• The client says it needs authentication or authorization: the connection was disconnected, expired, or never finished. Reconnect from the client; you'll get the consent screen again
• The client reports "rate limited" or a 429: the connector allows bursts of about 50 requests per 10 seconds per connection. The client should wait and retry; well-behaved ones do this on their own
• A write fails with a conflict: someone changed the item after the app read it. The app should read it again and reapply, which is the connector protecting newer work, not an error in your data
• You don't recognize a connection: disconnect it immediately, then change your password if you suspect it wasn't you

Where It's Available

The connector is included on every plan, Free, Starter, and Pro, under your plan's normal limits. It never unlocks anything your account couldn't already do.