Spine
Menu
Get started
← All guides

SPINE / Connection guide

Connect Spine to Codex

Add the Spine package, connect MCP and bring your project knowledge into Codex.

Documentation checked:

Before you begin

You need a Spine account with access to a base. Spine currently uses personal onboarding; contact us if you need access. Installing a plugin does not grant access to documents.

These steps follow the current OpenAI documentation. A new Spine deployment and real client authorization still need verification. Use the endpoint supplied during onboarding; the target for the new service is https://app.spine-kb.com/mcp.

Install the package

Spine’s package combines a skill with its remote MCP configuration. If you have access to the package repository, add its marketplace:

codex plugin marketplace add spine-kb/team-plugins

Open the plugin directory in a supported local client, select the Spine marketplace and install Spine. In Codex, open /plugins. Follow the connection and sign-in prompts for its MCP server. The repository must be accessible to your account; a private repository may require Git authentication.

Repository marketplaces are a distribution path for supported local clients. They do not automatically publish the plugin to the public directory or install it into every ChatGPT surface.

See OpenAI’s plugin packaging instructions for the current supported client surfaces and marketplace workflow.

If Spine is already connected

Start a new conversation and ask Codex to use Spine. Include the complete private document URL and your task if you have a starting document. The agent should use doc_open to open that link and follow the server’s current guide.

For example: “Use this Spine document as context and draft the next steps: [your private document URL].” The example is a prompt template, not a real document address.

Your base’s personal context document is part of agent bootstrap. It starts empty and can be updated through the agent, under your account’s permissions. The agent entry explains the intended workflow.

If something is missing

  • No Spine tools: check that the package is installed and enabled in this client.
  • A sign-in request: complete authorization with your own Spine account.
  • Access refused: check access to the requested base and document. Reconnecting does not create permission.
  • Several bases: include the relevant private link or base ID. An agent should ask when the target is genuinely ambiguous.

For the server’s current operation and document syntax contracts, use spine_guide. These pages teach connection and use; the server guide remains the technical reference.