MCP Server

claude — ~/projects/frontend

›look at my tickets in “To Do” and make a plan for how I should prioritize and finish them

janet-ai - list_tickets (MCP)(project_key: “SW”, status: “To Do”, assignees: [“me”])

You have 4 tickets in To Do. Here’s how I’d tackle them:

1. SW-84 SSO token refresh — blocking other auth work, fix first

2. SW-71 OAuth callback timeout — related to SSO, do right after

3. SW-63 Session cookie fix — standalone, quick win

4. SW-58 Safari redirect — lowest impact, last

Want me to spawn agents to start working through these?

›

Give AI agents like Claude Code, Cursor, and Codex full access to your Janet AI workspace. Create tickets, manage sprints, search across projects, resolve issues, and more.

Quick Setup (MCP)

The fastest way to connect your AI agent to Janet. One command installs, authenticates, and configures all your detected clients automatically (Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Codex).

pip install janet-mcp && janet-mcp-setup

Updating

janet-mcp-update

Or: pip install --upgrade janet-mcp, then restart your MCP client.

What You Can Do

Once connected, just talk to your AI agent naturally:

Use case	Example prompt
Find tickets	”Show me my assigned tickets in MAIN”
Search	”Search for tickets about authentication”
Create tickets	”Create a high-priority bug for the login redirect issue”
Schedule tickets	”Schedule a ticket for tomorrow at 9am to review the deployment”
List scheduled	”Show me all scheduled tickets in MAIN”
Reschedule	”Reschedule MAIN-1228 to next Friday at 3pm”
Activate scheduled	”Activate MAIN-1228 now”
Delete scheduled	”Delete scheduled ticket MAIN-1228”
Update tickets	”Move MAIN-452 to In Progress”
Manage sprints	”Add MAIN-100 and MAIN-101 to Sprint 3”
Add comments	”Add a comment to MAIN-100 saying the fix is deployed”
Break down work	”Create child tasks on MAIN-200 for each component”
Sort & organize	”Sort the To Do column by priority”
Understand context	”What are the highest priority bugs right now?”
Web search	”What are the best libraries for rate limiting in Node.js?”
Delete tickets	”Delete MAIN-452”
Restore tickets	”Restore MAIN-452”
Write docs	”Create a document called API Design with the proposed endpoint structure”
Update docs	”Update the Architecture doc with the new database schema”

Available Tools

The MCP server exposes 27 tools that your AI agent discovers and uses automatically:

Tool	Description
`get_workspace_context`	Lists all projects, statuses, and team members
`list_tickets`	Search and filter tickets. Single-status queries return kanban column order with position numbers. Set `scheduled_only` to list pending scheduled tickets instead
`get_ticket`	Full ticket details with description, comments, and child tasks
`create_ticket`	Create with title, description, status, priority, assignees, labels, sprint. Set `scheduled_activation_at` (ISO 8601) to hide the ticket until a future time — it activates automatically and sends a notification
`update_tickets`	Batch update status, priority, assignees, labels, due date. Set `scheduled_activation_at` to reschedule a pending ticket
`delete_tickets`	Soft-delete one or more tickets (restorable). Also deletes child tasks and sub-tasks
`restore_tickets`	Restore previously deleted tickets, including their child tasks and sub-tasks
`move_ticket`	Reposition (top/bottom/before/after), reorder columns, or sort by field. List tickets first for relative moves
`list_child_tasks`	List child tasks and their sub-tasks for a ticket
`manage_child_task`	Create, update, or delete a child task
`manage_sub_task`	Create, update, or delete a sub-task
`list_comments`	List comments with author, date, and content
`manage_comment`	Add, edit, or delete a comment
`list_sprints`	List sprints with status and dates
`manage_sprint`	Create or update a sprint
`manage_sprint_tickets`	Add or remove tickets from a sprint
`list_sprint_tickets`	List all tickets in a sprint, grouped by status column with position numbers
`list_documents`	List documents in the workspace
`get_document`	Get a document’s full content
`create_document`	Create a new document with a title and optional markdown content
`update_document`	Update a document’s title and/or content
`web_search`	Search the web for current information — best practices, libraries, error messages, documentation, news, etc.
`list_api_keys`	List all saved named keys and which one is currently active. Call before `switch_organization`.
`add_api_key`	Save a named API key to your local config. Use `switch_to=true` to activate it immediately.
`switch_organization`	Switch to a previously saved named key / organization without restarting the MCP server.
`remove_api_key`	Remove a saved named key from your local config.
`sign_out`	Clear the active key. Saved keys are preserved.

API Key Management

You can store multiple named keys and switch between organizations mid-session without restarting:

add_api_key(name="staging", key="jnt_...", switch_to=true)
switch_organization(key_name="prod")
remove_api_key(name="staging")
sign_out()

get_workspace_context shows the currently active key name.

Manual MCP Setup

If you prefer to configure manually instead of using the setup wizard:

1. Install

pip install janet-mcp

2. Generate an API Key

Go to your Janet AI dashboard → Organization Settings → API Keys → Generate Key.

3. Configure Your Client

claude mcp add janet-ai -e JANET_API_KEY=jnt_your_key_here -- janet-mcp

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "janet-ai": {
      "command": "janet-mcp",
      "env": { "JANET_API_KEY": "jnt_your_key_here" }
    }
  }
}

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "janet-ai": {
      "command": "janet-mcp",
      "env": { "JANET_API_KEY": "jnt_your_key_here" }
    }
  }
}

Add to .vscode/mcp.json:

{
  "servers": {
    "janet-ai": {
      "type": "stdio",
      "command": "janet-mcp",
      "env": { "JANET_API_KEY": "jnt_your_key_here" }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "servers": [
    {
      "name": "janet-ai",
      "type": "stdio",
      "command": "janet-mcp",
      "env": { "JANET_API_KEY": "jnt_your_key_here" }
    }
  ]
}

codex mcp add janet-ai -- janet-mcp -e JANET_API_KEY=jnt_your_key_here

API Keys

API keys are managed in Organization Settings → API Keys in your Janet AI dashboard.

Each key is scoped to a specific organization
Maximum 10 active keys per user per organization

Activity Log

Every MCP tool call is logged and visible in the MCP page → Usage tab in your dashboard.

Troubleshooting

Cannot reach the Janet API / DNS errors

If you see “Cannot reach the Janet API to validate your key” when the MCP server starts, your computer is likely unable to resolve the API hostname. This is a DNS issue — not a problem with your API key. The fix is to switch to a reliable public DNS resolver.

Mac
Windows

Open System Settings

Click the Apple menu → System Settings

Go to Network

Select Network in the sidebar → click your active connection (Wi-Fi or Ethernet) → Details

Open the DNS tab

Click the DNS tab

Add DNS servers

Click + and add both:

1.1.1.1 (Cloudflare)
8.8.8.8 (Google)

Apply

Click OK → Apply, then restart your MCP client

On older macOS using System Preferences: Network → select your connection → Advanced → DNS tab, then follow the same steps.

Open Network Connections

Press Win + R, type ncpa.cpl, and press Enter

Open adapter properties

Right-click your active network adapter (Wi-Fi or Ethernet) → Properties

Open IPv4 settings

Select Internet Protocol Version 4 (TCP/IPv4) → Properties

Set DNS servers

Select Use the following DNS server addresses and enter 1.1.1.1 and 8.8.8.8

Save

Click OK on both dialogs, then restart your MCP client

If the error persists after updating DNS, contact support@janet.ai with the full error message.

Getting started

Views

Agent Interactions

Ticket Features

Additional Features

Integrations

Migration

Quick Setup (MCP)

Updating

What You Can Do

Available Tools

API Key Management

Manual MCP Setup

1. Install

2. Generate an API Key

3. Configure Your Client

API Keys

Activity Log

Troubleshooting

Cannot reach the Janet API / DNS errors

Getting started

Views

Agent Interactions

Ticket Features

Additional Features

Integrations

Migration

​Quick Setup (MCP)

​Updating

​What You Can Do

​Available Tools

​API Key Management

​Manual MCP Setup

​1. Install

​2. Generate an API Key

​3. Configure Your Client

​API Keys

​Activity Log

​Troubleshooting

​Cannot reach the Janet API / DNS errors

Quick Setup (MCP)

Updating

What You Can Do

Available Tools

API Key Management

Manual MCP Setup

1. Install

2. Generate an API Key

3. Configure Your Client

API Keys

Activity Log

Troubleshooting

Cannot reach the Janet API / DNS errors