SPINE / Connection guide
Connect Spine to Claude
Install Spine's plugin and authorize its remote connector through your Claude account.
Documentation checked:
Before you begin
You need a Spine account and access to a base. Contact us for personal onboarding. The package repository must also be accessible to the account installing it.
This guide describes documented Claude setup paths. Installation, OAuth and bootstrap delivery against the new Spine deployment have not been tested. Use the MCP endpoint supplied during onboarding; the new service targets https://app.spine-kb.com/mcp.
Install the plugin and connect
In Claude on the web or desktop, open Customize → Plugins → Add → Add marketplace, enter https://github.com/spine-kb/team-plugins, and install Spine. Open the plugin’s Connectors tab, add or connect Spine, and complete OAuth with your own Spine account. Installing a package and authorizing the connector are separate steps.
A plugin installed through your Claude account is intended to follow that account across supported surfaces. A plugin installed only through the Claude Code CLI remains a separate local installation. See Claude’s plugin overview for the current installation and sync behaviour.
Connect a remote MCP directly
If you are setting up the connector separately, open Customize → Connectors, add a custom connector, enter the Spine MCP URL and follow the authentication steps. Team and Enterprise accounts may require an organization owner or an appropriate administrative role to add the connector first.
The remote connection is brokered through Claude’s infrastructure, so its server must be publicly reachable. A server reachable only on your laptop is a different setup. See Claude’s remote connector instructions.
Start working
Enable the connector for the conversation when required. Ask Claude to use Spine, and include the complete private document link and your task if you have one. A connected agent should open the link using doc_open, load the current server guide and read your personal context document for the selected base.
Without a starting link, state the task and base clearly. One unambiguous accessible base needs no extra choice; several possible bases may require clarification. Installing the connector does not expand your document permissions.
For bootstrap and public-link boundaries, see the agent entry. Current document syntax and operation contracts come from spine_guide, not a separate copy in the plugin.