Tideboard
Tideboard / MCP guide

Put your board
within your AI’s reach.

Connect your assistant, sign in to Tideboard, and work with your projects from chat. Start by asking it to list your projects or summarize your open cards.

Remote MCP endpoint · Streamable HTTP
https://tideboard.app/mcp

Connect once. Work from chat.

You need a Tideboard account and an AI client that supports remote MCP with OAuth. Client availability and organization policies can affect setup. The endpoint above is a protocol endpoint, not a page to open in your browser.

Claude web & Desktop

  1. Open Settings → Connectors and add a custom connector.
  2. Name it Tideboard and enter https://tideboard.app/mcp.
  3. Sign in to Tideboard and review the authorization screen.
  4. Enable the connector in your conversation and ask: “List my Tideboard projects.”

Claude’s setup guide

ChatGPT

  1. Open Plugins, select the plus button, then Add custom MCP server.
  2. Enter the Tideboard endpoint and select OAuth authentication.
  3. Create/install the plugin and complete the Tideboard sign-in and authorization flow.
  4. Enable it in a conversation and start with a read-only request.

Your workspace may restrict custom servers. Follow the current OpenAI setup guide if your UI differs.

Cursor

Add a remote MCP server in Cursor’s MCP settings, or add this configuration to .cursor/mcp.json:

{
  "mcpServers": {
    "tideboard": {
      "url": "https://tideboard.app/mcp"
    }
  }
}

Complete the OAuth sign-in when Cursor prompts you, then enable the server’s tools.

Cursor’s MCP guide

Other MCP clients

Use Streamable HTTP and the same endpoint. Tideboard advertises OAuth discovery metadata so compatible clients can start sign-in automatically.

OAuth uses an authorization code with PKCE. There is no personal token to copy for this setup. OAuth access tokens expire after 90 days; reconnect if authorization expires.

Personal bearer tokens are also accepted by the server where you already have one. Keep them out of shared configuration files.

Know what you are authorizing.

The assistant acts as your Tideboard user. Project membership and roles govern access to existing projects. The OAuth scope is mcp: it is not a per-project selection or a read-only permission. An authorized assistant can use the write tools your role permits.

Review write actions in your AI client.

Permanent deletion tools and member removal are unavailable through MCP; use the application interface for these actions. Archiving and other writes still require care: Tideboard does not enforce separate human approval for every write. Every registered tool call is audited without storing its arguments or results, and returned content is marked untrusted. These controls reduce risk but do not make prompt injection impossible.

Cards, comments, links and client-portal submissions can contain instructions written by other people. Treat that content as data, not authorization to act. Ask your client to confirm destructive or bulk changes and avoid unattended use of write tools with untrusted content.

Your chosen AI provider receives the tool results you ask it to access. Review its data handling policy before connecting confidential projects. To stop using the integration, disable it in your client; disconnecting a client is not a guarantee that an already-issued token has been revoked on the server.

What your assistant can do

The server exposes the following tools. Available actions depend on your role and the project’s settings; a viewer cannot perform member-only writes.

Cards
list_cardsget_cardsearch_cardsmy_taskscreate_cardupdate_cardmove_cardassign_memberunassign_memberarchive_cardassign_card_to_sprintlist_card_linkscreate_card_link
Comments
add_comment
Members
list_membersinvite_memberupdate_member_role
Projects
list_projectsget_projectcreate_projectupdate_project
Reviews
get_pending_reviewscomplete_reviewfail_review
Sprints
list_sprintscreate_sprint
Subtasks
set_subtask_completed

Start with a small, specific request.

Understand your work

“List my Tideboard projects, then show my urgent open cards in the Website project. Don’t change anything.”

Plan a change

“Draft three cards from these meeting notes. Show me the titles and descriptions before creating them in the Website backlog.”

PR review workflow

A configured review column can queue cards linked to GitHub pull requests. A connected agent claims work with get_pending_reviews, then reports completion or failure. The agent needs its own GitHub access to read or post reviews; connecting Tideboard alone does not grant GitHub access.

If the connection does not work

I see “Unauthorized” or a sign-in loop.

Use the exact HTTPS endpoint, complete the browser authorization, then reconnect. Expired OAuth tokens require a new sign-in. If the client never opens sign-in, check that it supports remote MCP OAuth and that your organization permits custom servers.

A tool returns “Forbidden” or cannot find a project.

Check which Tideboard account you authorized and whether it belongs to the project. Your membership role and project 2FA requirements still apply. Reconnect with the intended account.

I see “Too many requests”.

Pause and retry shortly. Avoid tight automatic retry loops or large parallel batches; MCP requests are rate limited.

The server URL does not show a web page.

That is expected: /mcp speaks MCP, while /docs/mcp is this human-readable guide. Add the server endpoint to your client instead of opening it as a normal page.

Setup guidance checked October 21, 2026. Client interfaces may change. Need help? Contact Tideboard.