Connect Syntra to Claude and ChatGPT
The Syntra connector lets Claude and ChatGPT work with your Syntra workspace through the open Model Context Protocol (MCP). Ask about projects, tasks, risks and sprints in plain language, and, where your workspace allows it, let the assistant create and update them for you.
Requirements
- A Syntra account that is a member of a workspace on the Enterprise plan. AI assistant connections come with the Enterprise plan, together with the API and webhooks. See pricing.
- Claude (any plan that supports connectors) or ChatGPT (a plan that lets you add a custom MCP server).
- Nothing to install, no OAuth app to register, no client ID or API key to create. You sign in to Syntra in your browser, pick the workspace and approve access once.
Server address: https://syntra.tymko.tech/mcp. You choose the workspace on the consent page when you connect. If you belong to several workspaces and prefer a separate connector for each, you can use a workspace’s own address instead, https://syntra.tymko.tech/mcp/<workspace>, shown in Syntra on the workspace’s API page. This is optional.
Connect in Claude
Syntra is listed in the Claude Connectors Directory as a community connector. Claude identifies itself to Syntra automatically with a Client ID Metadata Document, so there is no OAuth app, client ID or API key to set up. The connector works in Claude on the web, in Claude Desktop and in the mobile apps.
- Find Syntra.In Claude, open Customize (or Settings) → Connectors, search for Syntra and click Connect. You can also open the Syntra listing directly.
- Sign in to Syntra.A Syntra window opens; sign in with your Syntra account (and your second factor, if it is on).
- Pick the workspace and allow access.The consent page shows the app (Claude, claude.ai), your user, the access level and where you will be sent back. If you belong to several workspaces, choose one, then click Allow.
- Ask.In a new chat, ask about your projects. Claude calls the Syntra tools and shows each call it makes.
Claude Code connects the same way: claude mcp add --transport http syntra https://syntra.tymko.tech/mcp, then run /mcp to sign in.
Connect in ChatGPT
- Add a custom MCP server.In ChatGPT, open Plugins (Settings → Apps), click Add, then Add custom MCP server. Enter the URL
https://syntra.tymko.tech/mcpand choose OAuth as the authentication. - Sign in and allow.ChatGPT identifies itself automatically, so there is nothing to register in Syntra. Sign in to Syntra, pick the workspace and click Allow on the same consent page as for Claude; it names the app as ChatGPT (chatgpt.com).
- Use it in a chat.Mention Syntra or pick it from the tools menu, then ask your question.
Syntra is not in the ChatGPT app directory yet, so for now it is added as a custom MCP server.
Other MCP clients
Any client that supports remote MCP servers connects to https://syntra.tymko.tech/mcp with OAuth: the same sign-in and consent page as above. Clients that send their own headers can use a Syntra access key instead, as Authorization: Bearer syn_…. For example, Claude Code with a key: claude mcp add --transport http syntra https://syntra.tymko.tech/mcp --header "Authorization: Bearer syn_…". Workspace owners and admins issue keys in the workspace settings on the API tab; every member can create a personal key under Settings → API keys.
Tools
Every connection gets the read tools. The write tools appear only when the workspace has writing switched on and you allowed “read and write” on the consent page. No tool can delete anything.
| Tool | What it does |
|---|---|
list_projects | Projects you can see: code, name, status, progress, priority, quarter, leader, deadline, department, health lights, open risks. Read only. |
get_project | One project in full: description, budget, health lights, tasks per status, the tasks themselves and the risks with their mitigation. Read only. |
list_tasks | Tasks across your projects or in one project, newest changes first, filtered by project, status, assignee, sprint or date of change. Read only. |
list_sprints | Sprints per department with dates, status, task counts and Story Points. Read only. |
get_sprint | One sprint in full: goal, Story Points, its tasks and the burndown. Read only. |
whoami | Which user and workspace the connection acts as, and the role. Read only. |
create_task | Creates a task or a bug report in a project, as you. Write. |
update_task | Changes a task: title, description, status, assignee, deadline, tags, Story Points, sprint. Write. |
add_task_comment | Adds a comment to a task; the assignee and project leader are notified. Write. |
create_project | Creates a project with a description, status, priority, quarter, deadline and leader. Write. |
update_project | Changes a project's fields, health lights or budget. Write. |
add_risk | Registers a risk on a project with its severity and mitigation. Write. |
update_risk | Changes a risk's text, severity, mitigation or status (close or reopen). Write. |
create_sprint | Plans a new sprint for a department. Write. |
update_sprint | Changes a planned or active sprint's name, goal or dates. Write. |
Example prompts
- “Which projects are behind schedule this quarter, and why?”
- “What changed in the marketing projects since Monday?”
- “How is the current sprint going? Show the burndown and what is still open.”
- “Who has the most overdue tasks right now?”
- “Create a bug in project P-117: the checkout button does nothing on iOS, with steps to reproduce.”
- “Add a high risk to P-131: the supplier may miss the launch date; mitigation: a second supplier.”
Permissions
- Your rights, nothing more. The assistant acts as you inside the chosen workspace and sees exactly what your role allows; restricted projects stay hidden if you cannot open them.
- Read for every member. Members of workspaces on the Enterprise plan can connect and read.
- Writing only when both allow it. The write tools work only where a Syntra superadmin has switched MCP writing on for the workspace (the owner asks support) and you chose “read and write” on the consent page. Otherwise the connection is read only, whatever the assistant asks for.
- No deletions. No tool deletes projects, tasks, risks, sprints or comments.
- Connector only. Tokens issued to Claude and ChatGPT work only for the MCP connection, not for the rest of the Syntra API.
- Visible changes. Changes made through the connector appear in Syntra under your name, in the task and project history and in the audit log.
Privacy and data
Syntra sends the assistant only the results of the tools it calls, limited to what you can see. Syntra does not receive or store your conversations with Claude or ChatGPT; what the assistant does with tool results is governed by Anthropic's or OpenAI's terms for your account. Sign-in uses OAuth 2.0 with PKCE: the assistant never sees your Syntra password, and Syntra stores only hashes of the tokens it issues. Details are in the privacy policy, the sub-processor list and the DPA.
Disconnect
Remove the connector in Claude or ChatGPT, and withdraw the consent in Syntra under Settings → API keys → My consents. Every member does this for their own access. After that the assistant's refresh token stops working at once, and the current access token expires within 24 hours. A workspace owner can also ask support to switch writing off for the whole workspace.
Troubleshooting
“There is no workspace you can connect this app to”
None of your workspaces is on the Enterprise plan, or the workspace address in the connector URL is one you are not a member of. Ask the workspace owner, or connect with the general address https://syntra.tymko.tech/mcp.
The assistant says the connection is read only
Writing is off for the workspace, or you allowed read only. Ask the owner to have writing switched on, then disconnect and connect again and choose “read and write” on the consent page.
A project is missing from the answers
Ask the assistant to run whoami: it shows the user, workspace and role the connection uses. Projects you cannot open in Syntra are not visible to the assistant either.
Support
Write to support@tymko.tech with the time of the problem and, if possible, the tool name the assistant showed.