AI Specialists Hub - MCP Integration

Connection

Call the MCP endpoint via HTTP POST. The endpoint URL is stored in TOOLS.md or provided by the user.

CODEBLOCK0

Critical headers: Must include Accept: application/json, text/event-stream or the server returns 406.

Response format: SSE — parse with: response.split('data: ')[1] → JSON → INLINECODE2

Available Tools

Discovery & Management

Tool	Required Params	Description
INLINECODE3	—	List all hired specialists
INLINECODE4

— | List available specialist types |

Workspace Navigation

Tool	Required Params	Description
INLINECODE14	INLINECODE15	Full folder/file tree
INLINECODE16

specialist, folder_path | List folder contents |

Document Operations

Tool	Required Params	Description
INLINECODE19	INLINECODE20, INLINECODE21	Read one document
INLINECODE22

specialist, document_paths (array) | Bulk read multiple docs |

Folder Operations

Tool	Required Params	Description
INLINECODE32	INLINECODE33, INLINECODE34	Create folder (recursive)
INLINECODE35

specialist, folder_path | Delete folder and contents |

Parameter note: The specialist identifier is always the id field from list_specialists, not the display name. Use lowercase (e.g. ruby, peter, benjamin).

Working with a Specialist

Every specialist has an ai-instructions/ folder containing their identity and behavioral instructions. Always read these first when working with a specialist you haven't loaded yet:

CODEBLOCK1

Pattern: First interaction with a specialist

1. 1. list_specialists → find the specialist id
2. INLINECODE45 → read ai-instructions/core-instructions.md and INLINECODE47
3. Understand their domain, workspace structure, and communication style
4. INLINECODE48 → see their full workspace
5. Now you can work with their data informed by their context

Pattern: Quick data retrieval

1. 1. explore_specialist_tree → find the files you need
2. INLINECODE50 → bulk read (more efficient than individual reads)
3. Summarize for the user

Pattern: Updating specialist data

1. 1. Read the existing document first
2. Modify content as needed
3. INLINECODE51 → write back (creates if new, overwrites if existing)
4. For new folders: create_specialist_folder first, then write documents into it

User Signup (Agent-Initiated Onboarding)

If your human doesn't have an AI Specialists Hub account yet, you can create one via the public signup API:

CODEBLOCK2

Response (201):
CODEBLOCK3

⚠️ CRITICAL: Credential Handoff

You MUST provide all credentials to the human. Whether you auto-generate the username/email/password or ask the human to choose them, the human must receive:

1. 1. Username — for web dashboard login at aispecialistshub.com
2. Email — used for account verification
3. Password — for web dashboard login
4. MCP key — for connecting AI tools to their specialists

Never keep credentials from the human. They own the account. Present all four clearly after signup.

Unverified Accounts

• - Limited to 2 specialists (default: Friday is auto-hired)
• Full MCP access — specialists work immediately
• Can log in to web dashboard with username/password
• Verify email for full access (more specialists)

Signup Flow

1. 1. Confirm the human wants an AI Specialists Hub account
2. Collect or generate: username, email, password
3. Call INLINECODE53
4. Give the human ALL credentials (username, email, password, MCP key)
5. Store the MCP endpoint URL in your config: INLINECODE54
6. Start using specialists via MCP

Configuration

Store the MCP endpoint URL in TOOLS.md:

CODEBLOCK4

See references/specialists-guide.md for details on specialist workspace conventions.