Services

The goal of the Services page is simple: connect external capabilities so your agent can call them during real tasks.

Page map

After opening Services in the left sidebar, focus on these areas:

1. Top-right actions: Refresh, Search services, New service.
2. Connected services area: grouped by type, usually MCP, API, LOCAL.
3. Recommended services area: click + for fast setup.
4. Service card status: green dot usually means online and available.

Quick connect recommended services

Best for common tools like GitHub, Notion, Jira, Slack, and Google Drive.

1. Find the target service card in the lower area.
2. Click + on the right.
3. Finish auth; the service appears in connected groups above.
4. Use Search services to confirm it is visible.

Create a new service

Best when recommended services do not cover your use case.

1. Click New service.
2. Describe your target directly in chat, for example:
   • Add MCP Server to add a Linear MCP service.
   • Connect a local Obsidian service to read my knowledge base.
   • Add a Jira API service for tasks in a specific project.
3. Wait for the agent to generate and execute config.
4. Return to Services and verify the card + status dot.

Auto-run mode recommendations

• Daily additions: enable Auto-run for speed.
• Sensitive permissions: disable Auto-run and confirm each action.
• Multi-step setup: keep Todo view open to track sub-steps.

Manage connected services

1. Use Search services to locate a specific service quickly.
2. If status looks off, click Refresh first.
3. Manage responsibilities by group:
   • MCP: protocol-level external integrations, such as Linear MCP.
   • API: standard HTTP API capabilities, such as GitHub/Jira.
   • LOCAL: local apps/resources, such as Obsidian.

Post-connect validation

For every new service, run one minimum verification:

1. Send a real task in chat, for example:
   • Read recent GitHub commits and summarize risk points.
   • Pull this week’s project plan from Notion.
   • Get my assigned TODOs from Linear.
2. Check execution logs for the service call.
3. Move to the next integration only after results are reproducible.

Common issues

1) Clicked + but it does not appear in connected list

• Click Refresh first.
• Use Search services for exact lookup.
• Re-authorize and confirm account/workspace match.

2) Shows connected but fails at runtime

• Most cases are missing scopes; add read permissions and retry.
• For MCP services, verify the target MCP server is online.
• For local services, verify local app is running and paths are accessible.

3) New service flow gets stuck in chat

• Rewrite with a shorter single-goal prompt.
• Disable auto-run and confirm actions step by step.
• Create a minimum viable service first, then add capabilities incrementally.

Next step

• Go to Skills and package validated service workflows into reusable skills.