Skip to main content
ShipOS exposes an MCP server for workspace-scoped reads and approved writes. You can connect with either an API key (simplest, works in any client) or OAuth (used by ChatGPT). The MCP page in the dashboard shows the server endpoint.
Treat the MCP endpoint like an integration secret. It can expose workspace context after authorization, and write tools should only be used by trusted operators.

​
Connect with an API key

Use this for clients that don’t support OAuth, including Warp and most terminal-based assistants.
1

Create a Console API key

In the Shipyard Console, open API Keys and create a new key. Copy it immediately — the full value is only shown once.
2

Configure your MCP client

Point your client at https://mcp.shipyard.lol/api/mcp and send the key in the Authorization header.
{
  "mcpServers": {
    "shipyard": {
      "url": "https://mcp.shipyard.lol/api/mcp",
      "headers": {
        "Authorization": "Bearer sh_your_api_key"
      }
    }
  }
}
3

Revoke when rotating

Revoke unused or exposed keys from the Console API Keys page.

​
Connect with OAuth

Use this for ChatGPT and other clients that natively support MCP OAuth.
1

Open MCP Server in ShipOS

Go to Dashboard → MCP Server and copy the ShipOS server endpoint.
2

Register the endpoint

Add ShipOS as a custom MCP server in ChatGPT or another compatible client.
3

Authorize in the browser

Complete the OAuth prompt, then return to the MCP client.
4

Start read-only

Verify issue, project, message, and Company Knowledge reads before allowing mutation workflows.

​
Available tools

Read tools

Search issues, get an issue by ID, search projects, search Company Knowledge, search messages, and list ShipCode agents.

Write tools

Create issues, update issue fields, create notes or messages, and update Company Knowledge for admins.

​
Tool names

search_issues, get_issue, search_projects, search_company_knowledge, search_messages, and list_agents.
create_issue, update_issue, create_note_or_message, and update_company_knowledge.