MCP (Model Context Protocol)

Tulsk uses the Model Context Protocol (MCP) as its integration layer. MCP is an open standard for connecting AI tools to external services.

What is MCP?

MCP provides a standardized way for AI models to discover and use tools. Instead of hardcoding API calls, AI tools connect to an MCP server that advertises available tools with their parameters and descriptions.

Tulsk’s MCP server

Tulsk exposes an MCP server at /api/mcp/sse (Server-Sent Events transport). It provides 21+ tools organized by category:

Read-only tools

get_projects — list projects in the workspace
get_project_by_id — project details with recent tasks
get_task_context — full task info with comments
web_search — search the public web
open_page — navigate to a Tulsk page

Agent awareness

list_agents — all agents with status, skills, run count
get_agent_detail — full agent config and health
get_agent_runs — recent runs filtered by agent/task/status
get_run_result — check status and output of a specific run

Agent control

trigger_agent_run — queue an agent to work on a task
assign_task_to_agent — assign + trigger in one step
cancel_agent_run — cancel a pending/running run

EMA PM tools

get_agent_activity_summary — detailed stats by agent/project
get_delegation_tree — trace agent-to-agent delegation chains

EMA scheduled reports

create_ema_schedule — create a recurring report schedule
list_ema_schedules — view all schedules
cancel_ema_schedule — deactivate a schedule

Action tools

create_project — create a new project
create_task — create a task in a project
update_task — modify task status, priority, assignees
add_comment — post a comment on a task

Connecting external AI tools

Any MCP-compatible client can connect to Tulsk:

Claude Desktop

Add to your Claude Desktop MCP config:


{
  "mcpServers": {
    "tulsk": {
      "transport": "sse",
      "url": "https://your-tulsk-instance.vercel.app/api/mcp/sse"
    }
  }
}

Cursor

Cursor supports MCP servers natively. Add the SSE URL in Cursor’s MCP settings.

Any MCP client

Connect via SSE transport to /api/mcp/sse. Authentication is handled via Clerk cookies.