Skip to content
tgethr
tgethr home

Connect your agent to tgethr.

Let your agent work with your projects, tasks, and contacts through the tgethr MCP server.

MCP server URL

https://app.tgethr.com/mcp

Transport: Streamable HTTP. Authentication: OAuth.

For agents reading this page: read the plain-text connection and tool instructions. The address above is the server endpoint to give your MCP client.

Connect from your agent app

  1. Open your app's remote MCP connections and add https://app.tgethr.com/mcp.
  2. Choose OAuth. Leave client ID and client secret blank if your app supports automatic client registration.
  3. Follow the sign-in link to tgethr, choose your account, review the requested permissions, and click Connect.
  4. Have your agent call connection_info to confirm the account, then list_records with {"resource":"projects"}.

You need an existing tgethr account and an app that supports remote MCP with OAuth. Reading this page does not install tools or grant access. Your app handles sign-in and stores credentials; you do not need to paste a password or token into a chat.

Work with your account

Agents can read the projects, tasks, discussions, events, contacts, and deals you have access to. With your permission, they can create and update supported records, draft documents, suggest document changes, and move supported records to Trash.

Start with connection_info for the account and teammate IDs. Use list_records and get_record to find existing work. Before a change, use describe_records for the allowed fields and check the current tool list for document operations.

To list a project's tasks, call list_records with resource: "todos" and its project_id. Results are paginated: follow next_page until it is null. Check for duplicates before creating records or retrying an uncertain change.

Access follows your current account role and project invitations. Changes can notify teammates and trigger configured webhooks. You can disconnect an agent in tgethr Settings under Integrations.

Building a connection?

The server supports automatic public-client registration and the OAuth authorization-code flow with S256 PKCE. Request tgethr:read, plus tgethr:write when changes are needed. Use https://app.tgethr.com/mcp as the OAuth resource value for authorization, token exchange, and refresh.

An unauthenticated request to the MCP server returns an OAuth challenge. That means sign-in is required. If a connection has no tools, check server discovery and tools/list, then refresh the connection in your app. Reconnect if access has expired or been revoked.