Project management MCP server: what OIO's exposes and how to connect

OIO runs an MCP server at https://oio.app/api/mcp. Connect your own AI assistant to it and the assistant can read your projects and tickets and update the ones you own. This page lists every tool, shows the config, and explains the security model in plain words.

7 min read

By · Updated

The short answer

A project management MCP server is a web address your AI assistant can call to read and change your projects. OIO's is at https://oio.app/api/mcp. It offers ten tools: list projects, list and read tickets, create tickets, add notes and to-dos, tick to-dos off, change a ticket's status, post a status line for the client, and fetch the client's status link.

You connect once. Claude signs in with OAuth. Cursor and most other apps use a personal access token from Settings, then Connections. Full access is on the Studio plan ($99 a month, 5 seats).

What MCP is

MCP stands for Model Context Protocol. It is an open standard for letting an AI assistant call tools in other software. The software runs a server. The server publishes a list of named tools, each with a short description and a fixed set of inputs. The assistant reads the list, picks the tool that fits what you asked, and calls it.

Two things follow from that. The assistant can only do what the list allows. If there is no delete tool, it cannot delete. And the assistant does the typing, not the deciding. You still say which job, which tickets and which dates.

Without MCP, the plan an assistant writes stays in the chat. You copy it into your project tool by hand, one ticket at a time. With MCP, the assistant writes the tickets into the right project itself, where your team and your client already look.

The ten tools OIO's server exposes

This is the complete list, taken from the server code. Three read, seven can change data.

ToolWhat it doesChanges data
list_projectsYour active projects, ones shared with you and ones you follow as a client, with dates and whether you can change themNo
list_ticketsThe tickets on one project, newest first, with status, dates and to-do counts; filter by statusNo
get_ticketOne ticket's name, status, dates, to-dos and noteNo
create_ticketA new ticket on a project you own, with a due date (tomorrow if none is given)Yes
add_todoOne to-do at the end of a ticket's checklistYes
complete_todoMarks a to-do done, or open againYes
add_ticket_noteAppends a dated paragraph to a ticket's note; never edits what is thereYes
set_ticket_statusNew, in progress, problem, on hold, done or infoYes
post_status_updateOne short status line on the project, visible to the client on their status linkYes
get_status_linkThe existing password-protected status link for the project's clientNo

What that looks like in a working week:

  • "Which tickets on the Riverside Tower job are on hold?" The assistant calls list_projects, then list_tickets with the hold filter.
  • "Here are my notes from the kickoff call. Make a ticket for each deliverable, due on the dates we agreed." It checks the existing tickets first, then calls create_ticket once per deliverable.
  • "Add the five render passes as to-dos on the lobby ticket." Five add_todo calls.
  • "The client approved the lobby still. Mark it done and tell them the next one is due Friday." set_ticket_status, then post_status_update.

There is no tool for projects, clients, quotes, invoices, files, sharing or settings. You create the project in OIO, then point the assistant at it.

How to connect

Every client uses the same server address. What differs is how it signs in.

Claude: OAuth, no token

In Claude (web, desktop or phone), open Settings, then Connectors, and add a custom connector. Paste https://oio.app/api/mcp and press Connect. Claude opens an OIO sign-in page. Sign in, choose whether the assistant may make changes, and press Allow.

Behind that screen the server does what the MCP authorization spec asks. Claude finds the sign-in server from the metadata at /.well-known/oauth-protected-resource/api/mcp. It registers itself, either with a client metadata document or through dynamic client registration at /api/oauth/register. The sign-in uses PKCE, and the access token lasts one hour before Claude refreshes it.

For Claude Code, one command does the same, then run /mcp to sign in:

claude mcp add --transport http oio https://oio.app/api/mcp

The full Claude and ChatGPT walkthrough, with the menus as of October 2026, is in project planning with AI.

Cursor and other apps: a personal access token

In OIO, open Settings, then Connections, and choose New connection. Name it after the app, for example "Cursor on the studio iMac". Leave "Can make changes" on, or turn it off for read only. Pick an expiry: 30 days, 90 days, 6 months or a year. Copy the token. It starts with oio_pat_, and OIO shows it once.

For Cursor, put this in .cursor/mcp.json:

{
  "mcpServers": {
    "oio": {
      "url": "https://oio.app/api/mcp",
      "headers": { "Authorization": "Bearer oio_pat_YOUR_TOKEN" }
    }
  }
}

For Claude Desktop with a token instead of the connector, claude_desktop_config.json runs the mcp-remote bridge:

{
  "mcpServers": {
    "oio": {
      "command": "npx",
      "args": ["mcp-remote", "https://oio.app/api/mcp", "--header", "Authorization:${OIO_AUTH}"],
      "env": { "OIO_AUTH": "Bearer oio_pat_YOUR_TOKEN" }
    }
  }
}

The same three snippets, with your token filled in, are on the Connections page after you create it.

The security model, in plain words

The first question about any project management MCP server is what it can reach. Here is the honest answer for OIO's.

  • Your data only. Each call runs as you, through the same database rules as the app. The assistant sees what you see in OIO and nothing more. There is no input for another user's id, and a ticket you cannot see gets the same "not found" answer as one that does not exist.
  • Changes only where you own the project. Projects shared with you, and projects you follow as a client, are read only through the connection.
  • Nothing you cannot undo. No tool deletes, shares, sends money or changes settings. A note is only ever appended to.
  • Every change is logged. It shows in your Logs with the connection's name, so you can tell "Cursor on the studio iMac" from your own edits.
  • Tokens you control. Up to ten live connections. Each one is read only or read and write, expires on the date you picked, and can be revoked in Settings, then Connections, with one click. OIO keeps only a hash of the token, not the token itself.
  • Rate limits. Each connection gets 60 calls a minute and 2,000 a day, with 5,000 a day per user across all of them.
  • Server to server only. A request from a web page is refused, so a site you visit cannot use your token.

One risk stays with you. Ticket notes are sometimes written by clients or freelancers, and a note could contain text that reads like an instruction to an AI. The server labels that text as untrusted for the assistant. No label is perfect, so read what the assistant says it did.

What the assistant reads also goes to its provider: Anthropic for Claude, and Cursor plus the model you picked in it for Cursor. That is the same as pasting the text into the chat yourself. OIO does not pass your data to an AI provider of its own through this connection.

Plan requirement

Full tool access needs the Studio plan, $99 a month with 5 seats and a 7-day trial. Accounts still on the older Pro plan keep it too.

On Free, Lite and Solo, a personal access token works only for the tools the free Blender add-on uses: list_projects, list_tickets, set_ticket_status, post_status_update and get_status_link. OAuth connections such as Claude's connector are refused on those plans. The server checks your plan on every call, so a downgrade takes effect at once.

When it does not work

  • 401 Unauthorized: the token is wrong, revoked or expired. Create a new one in Settings, then Connections.
  • 402: the account is below Studio and the app signed in with OAuth.
  • 403 with "This connection is read-only": the token or the Allow screen gave read access only. Make a new connection with changes allowed.
  • 429: the per-minute or per-day limit. Wait a minute, or until the next day for the daily cap.
  • "Not found, or you can't change it": the project is shared with you, not yours. Ask the owner to make the change, or do it in the app.

If you are pricing the job before you plan it, the quote template covers that, and the invoice generator covers the end. For ideas on what to ask the assistant once it is connected, see AI workflows for 3D and archviz studios.

Questions

What is a project management MCP server?

A web address that lets an AI assistant call named tools in a project tool, such as list tickets or create a ticket. OIO's is at https://oio.app/api/mcp and offers ten tools.

Can I connect Claude to OIO without a token?

Yes. Add https://oio.app/api/mcp as a custom connector in Claude, sign in to OIO and press Allow. Tokens are for Cursor and other apps that do not do the sign-in.

Can the AI delete my projects or tickets?

No. OIO's server has no delete, sharing, money or settings tools. It can create tickets, add notes and to-dos and change statuses, only on projects you own.

Which OIO plan includes the MCP server?

Studio, at $99 a month, and the older Pro plan. Lower plans can use a token only for the free Blender add-on's five tools.

Free tools for this

OIO for agencies and studios

OIO is project management for agencies and studios: one page per client job, tickets on a kanban and a timeline, freelancers on a ticket link and a status link for the client. On Studio, your own AI assistant can read and update it over MCP. Free for one project, no card. Create a free account.

Add OIO as a preferred source on Google

More guides