Claude · Remote MCP
Claude Setup
Connect Claude via remote MCP, with REST as a fallback.
Connection endpoints
AiM Continuity API base URL
/apiOpenAPI schema URL
/api/openapi.jsonMCP server URL
/mcpCopy these into your Claude configuration. The actual API key is never shown here.
Supported connection methods
Setup steps
- 1.Open your Claude project or workspace connectors.
- 2.Add a new remote MCP server using the AiM MCP server URL.
- 3.Configure authentication with the Bearer token from your AiM credential.
- 4.Claude will only see the approved AiM tools (read + recommend) — never delete or approve tools.
- 5.Run the connection test.
Authentication
- ·Authentication: HTTP Bearer token on the MCP endpoint.
- ·Add the key to the connector's Authorization header.
- ·Only approved AiM tools are exposed — no delete, approve, or admin scopes.
Example request
POST /api/continuity/intake
Authorization: Bearer YOUR_AIM_CREDENTIAL
Content-Type: application/json
{
"provider": "claude",
"conversation": { "title": "Strategy sync" },
"organization": { "primary_project": "Website Redesign" },
"tasks": [{ "title": "Follow up with design", "status": "OPEN" }],
"recommendations": [{ "action": "ASSIGN_TO_PROJECT", "confidence": 0.8 }]
}Claude setup prompt
Paste this into Claude's system / instructions so it knows how to push conversations, decisions, tasks, and ideas into AiM Continuity as PENDING REVIEW.
You're connected to AiM Continuity via MCP. Whenever I discuss work — a
conversation, decision, task, idea, asset, or project — call the
submit_continuity_recommendation tool to send it to AiM as PENDING REVIEW.
First call search_continuity and get_projects to check for existing records.
If something already exists, recommend UPDATE EXISTING rather than a new
record. Every submission must be framed as a recommendation pending human
approval — never say it's approved or final.
When you create a recommendation, include:
- conversation title + summary
- primary_project, workstream, related_projects
- detected decisions, tasks, ideas, assets
- a recommended action (e.g. ASSIGN_TO_PROJECT, CREATE_WORKSTREAM, CROSS-REFERENCE)
- a reason and a confidence score (0-1)First connection test
After connecting, have Claude run these two prompts. The second must land as PENDING REVIEW — never auto-approved.
Guided setup
Prefer a guided flow? Use the connection wizard to choose a method, create a credential, test, choose permissions, and finish — in six steps.
Open the wizardPrinciple
AI Recommends. Humans Decide. Claude may read organizational records and submit recommendations, but may never delete, approve its own work, or change configuration.