MCP Integration

Tycana exposes a full Model Context Protocol server. Connect your AI assistant and manage tasks with natural language — add tasks, check what’s due, mark things done, all through conversation.

Requirements: Tycana Sync subscription ($6/mo) and an MCP token from your dashboard.


Setup

1. Get your MCP token

Log in to app.tycana.com, go to MCP Tokens, and generate a new token. Copy it — you’ll need it for the next step.

2. Connect your AI assistant

Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "tycana": {
      "type": "streamable-http",
      "url": "https://app.tycana.com/mcp",
      "headers": {
        "authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Config file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

Restart Claude Desktop after saving.

Claude Code (CLI)

claude mcp add tycana \
  --transport streamable-http \
  https://app.tycana.com/mcp \
  --header "authorization: Bearer YOUR_TOKEN_HERE"

Other MCP clients

Any MCP-compatible client can connect. The server URL is:

https://app.tycana.com/mcp

Authentication: Bearer token in the authorization header. Transport: Streamable HTTP.


Tools

Nine tools with full read and write access to your tasks and spaces.

ToolWhat it does
list_tasksList tasks with optional filters (space, project, status)
add_taskCreate a task with title, due date, project, tags, notes, recurrence
complete_taskMark a task done by ID or title search
edit_taskUpdate a task’s title, due date, project, or notes
delete_taskPermanently remove a task
search_tasksSearch tasks by title across all spaces
get_spacesList your spaces and roles
get_calendar_urlGet the calendar subscription URL for a space
pingHealth check — verify your connection works

Example prompts

Once connected, just talk to your AI assistant naturally:

  • “Add a task to review the API docs by Thursday.”
  • “What’s overdue in my work space?”
  • “Mark the deploy task done.”
  • “Show me everything due this week.”
  • “Create a recurring task for daily standup at 9am.”
  • “Move the client call to Friday.”
  • “What’s on my plate today?”
  • “Delete the old planning task.”

Your AI assistant figures out which tools to call. You don’t need to learn the tool names.


Troubleshooting

“Authentication failed” — Check that your token is correct and includes the tyk_ prefix. Generate a new one from app.tycana.com if needed.

“Connection refused” — Verify the URL is https://app.tycana.com/mcp (not /api/mcp or other variations).

Tools not appearing — Restart your AI assistant after adding the configuration. Claude Desktop requires a full restart.

“Unknown tool” errors — Make sure you’re using the latest configuration. The server exposes 9 tools automatically on connection.

Token not working after regeneration — Old tokens are revoked immediately. Update your configuration with the new token and restart your AI assistant.


How it works

Tycana’s MCP server uses Streamable HTTP transport. When your AI assistant connects, it discovers all 9 tools automatically. Each request is authenticated with your token and scoped to your account — your assistant can only see and modify your tasks.

The server lives at app.tycana.com/mcp alongside the sync API. Same infrastructure, same security, same data. A task added through MCP shows up in your CLI and on your calendar immediately.

Your data stays yours. We don’t send your tasks to AI providers. The MCP connection is between your AI assistant and our API — initiated by you, authenticated with your token, revocable at any time.


MCP requires a Sync subscription. See pricing →