MCP

Trellis MCP turns your workspace into something an AI assistant can actually work in, not just look at. Instead of tabbing between Claude and Trellis to translate a conversation into action, ask your assistant to do the work directly: create the bug you just spotted, update the deliverable that slipped, log the 45 minutes you spent on a call, or draft this fortnight's client update using real data from the project.

Every action runs as you: your OAuth session, your role, your project memberships, your rate card. The assistant sees only what you'd see in the app and can't reach anything gated behind a permission you don't have.

Tool responses come back whole. A task fetch pulls its status, dates, assignee, budget, and spend along with it, so treat what you ask about the same way you'd treat pasting it into the chat: that's what the model will see.

You can disconnect any client from its own connector settings any time. Trellis can also turn the AI Agents add-on off at the workspace level. Either kills every active session immediately.

What you can do

Tasks. Create tasks, bugs, and deliverables; update any field on an existing task; pull full detail on a single task; list recent work in a project; search by title or description across every project you can access; and see everything currently assigned to you. Archive tasks when they're recoverable, delete them when they're not.

Sprints and workflow. List a project's sprints, workflow columns, and members, so new tasks land in the right sprint, the right status, and the right person's queue. Create sprints, rename them, move their dates, start and complete them, and move tasks into a sprint, out to the backlog, or to an exact position alongside the work already in it.

Comments. Post comments, reply in threads, edit or delete your own, and react with emoji.

Time tracking. Log hours against a task, review your own entries over any date range, and correct or remove them.

Reporting. Generate a client-ready project update for any date range: executive summary, completed work, items in progress, blockers, and decisions needed, with optional spend and timeline data.

Connecting a client

Trellis MCP uses OAuth 2.1. Clients register themselves and you approve access from a consent screen.

Connect using the Claude directory

Trellis is listed in the Claude connector directory, so on Claude there's nothing to paste in by hand.

Connect manually

Claude (web / desktop / mobile)

Claude Code

Run in your terminal:

claude mcp add --scope user --transport http trellis https://trellisapp.co.uk/api/v1/mcp

Then run claude and use /mcp to complete the OAuth handshake in your browser.

Codex / Codex CLI

Follow the same pattern using the Codex MCP configuration flow, pointing to the same URL. Trellis will show a "Codex" branded consent screen.

Once connected, ask your assistant to do things by name: "create a bug on the Website Refresh project titled 'Cart total incorrect on Safari'", "log 45 minutes against WR-142", "give me a client update for the last two weeks on Q3 Marketing".

Available tools

Projects

• list_projects — list every project in the current workspace.

Tasks

• list_issues — recent tasks in a project, newest updates first.
• search_issues — free-text search by title or description across every project you can access.
• get_my_issues — every task currently assigned to you.
• get_issue — full detail on a single task by code.
• create_issue — create a new task, bug, or deliverable, optionally at a chosen position inside a sprint.
• update_issue — update any field (status, assignee, dates, estimate, description, timeline bar colour, etc.).
• archive_issue — soft-delete, children archived alongside, recoverable.
• delete_issue — permanent delete, children detached, irreversible.

Timeline

• list_milestones — a project's milestones, with the id needed to update or delete one.
• create_milestone — add a milestone on a single date, with an optional colour and note.
• update_milestone — change a milestone's name, date, colour, or note.
• delete_milestone — remove a milestone. Irreversible.
• list_dependencies — the dependencies on a project's timeline, as issue-code pairs with type and lag.
• create_dependency — link two issues in the same project. Defaults to finish-to-start.
• delete_dependency — remove the link between two issues. To change a dependency's type or lag, delete it and create it again.

Colours accept a hex code like #74a8e7 or a plain name — red, orange, amber, yellow, green, teal, blue, purple, pink, grey (gray works too). This applies to milestone colours and to the color field on a task, which is the colour of its timeline bar.

Sprints and workflow

• list_sprints — sprints in a project, so new tasks land in the right one.
• create_sprint — create a sprint in a project. New sprints always start as not-started.
• update_sprint — rename a sprint, change its dates, or start and complete it.
• move_issues_to_sprint — move one or more tasks into a sprint, optionally to the top, the bottom, or next to a task already in it. Moving tasks out of a sprint means targeting that project's backlog.
• list_workflow_statuses — status columns for a project (needed when setting status on create/update).
• list_project_members — project members (needed when assigning a task).

Comments

• create_comment — post a comment or reply in a thread.
• update_comment — edit a comment you authored.
• delete_comment — delete a comment you authored.
• add_comment_reaction — react with an emoji or shortcut like thumbs_up.
• remove_comment_reaction — remove a reaction you added.

Time tracking

• log_time — log hours against a task for yourself. Requires a rate card and salary on your profile.
• get_my_timelogs — your own time logs, newest first, optionally filtered by date range.
• update_my_timelog — correct start/end times on one of your own entries.
• delete_my_timelog — remove one of your own entries. Irreversible.

Reporting

• get_project_update — generate a client-ready project update for a date range (executive summary, completed work, in-progress, blockers, decisions needed, with optional spend and timeline).

Permissions and scopes

Every tool runs as you, using your workspace role and project memberships. If you can't do something in Trellis, the assistant can't either.

Trellis groups tools into seven scopes:

Clients request the scopes they need at connection time. You see them on the consent screen before approving.

The sprint tools sit under issues:write alongside the task tools, so a client that already has it needs no new approval.

Rate limits

Trellis MCP is rate-limited to 120 requests per minute per authenticated user. Requests over the limit return HTTP 429. Bursts are fine; sustained traffic should stay under the cap.

Troubleshooting

• "Missing rate card or salary" when logging time — log_time requires both on your profile. Ask a workspace admin to set them via Settings → Members.
• "Not authorized" on a project — the assistant only sees projects you're a member of. Ask an admin to add you.
• Assistant returns a stale task list — MCP results are live, but if you've just made changes in the UI, ask the assistant to list_issues again to refresh.