Skip to Content
IntegrationsMCP (Model Context Protocol)

MCP (Model Context Protocol)

Tulsk uses the Model Context Protocol (MCP) as its core integration layer, enabling a standardized way to connect AI tools with your workspace data and agent infrastructure.


What is MCP?

MCP provides a standardized protocol for AI models to discover and interact with tools. Instead of custom API integrations, AI clients connect to an MCP server that advertises its capabilities, parameters, and descriptions dynamically.


Tulsk’s MCP Server

Tulsk exposes a high-performance MCP server at /api/mcp/sse using the SSE (Server-Sent Events) transport.

Workspace Visibility

  • get_projects: List all active projects.
  • get_project_by_id: Fetch detailed project metadata and recent tasks.
  • get_task_context: Retrieve full task threads and comments.
  • web_search: Perform real-time web searches.
  • open_page: Navigate to specific Tulsk dashboard views.

Connecting External Clients

You can connect any MCP-compatible client to Tulsk for seamless tool access.

Claude Desktop

Add the following to your Claude Desktop configuration:

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

Cursor & IDEs

Cursor and other modern IDEs support MCP natively.

Open Settings

Navigate to the MCP or AI settings in your editor.

Add Server

Click Add New MCP Server.

Configure SSE

Select SSE as the transport type and paste your Tulsk API endpoint.

Authenticate

Authentication is handled automatically via your active browser session (Clerk).

Ensure your Tulsk instance is publicly accessible if you are using cloud-based AI clients.

Last updated on