Telos MCP Server

A Model Context Protocol (MCP) server that provides access to Telos project management tools. This server allows AI assistants to interact with Telos tickets, documentation, and project tasks.

Features

This MCP server provides 8 tools for managing Telos projects:

Core Tools

1. ask-question - Ask questions about tickets and get AI-powered answers with context
2. get-ticket-details - Retrieve full ticket information including description and comments
3. add-ticket-comment - Add comments to existing tickets
4. get-next-task - Get the next prioritized task for a specific application

Development Tools

5. get-git-branch-for-ticket - Get the correct git branch name for ticket development
6. mark-ticket-as-blocked - Mark tickets as blocked with a reason
7. add-documentation - Create knowledge tickets with documentation content
8. update-action-item - Update the status of action items in tickets

Installation

Using with MCP Clients

Add to your MCP client configuration:

Claude Desktop

Update your ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "telos": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-telos"],
      "env": {
        "TELOS_PERSONAL_ACCESS_TOKEN": "<YOUR_PAT_TOKEN>"
      }
    }
  }
}

Cursor MCP

Update your ~/.cursor/mcp.json:

{
  "mcpServers": {
    "telos": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-telos"],
      "env": {
        "TELOS_PERSONAL_ACCESS_TOKEN": "<YOUR_PAT_TOKEN>"
      }
    }
  }
}

Local Development

# Clone the repository
git clone <repository-url>
cd telos-mcp

# Install dependencies
npm install

# Build the project
npm run build

# Run locally
TELOS_PERSONAL_ACCESS_TOKEN=pat_your_token_here node build/index.js

Configuration

Required Environment Variables

• TELOS_PERSONAL_ACCESS_TOKEN - Your Telos Personal Access Token (starts with pat_)

Optional Environment Variables

• TELOS_BASE_URL - Base URL for Telos instance (defaults to https://go.telosready.com)

Getting Your Personal Access Token

1. Log into your Telos instance
2. Go to Account → Personal Access Tokens
3. Create a new token with a descriptive name
4. Copy the token (it starts with pat_)
5. Use it in your MCP configuration

Tool Usage Examples

Add a Comment to a Ticket

{
  "name": "add-ticket-comment",
  "arguments": {
    "ticketReference": "TEL037",
    "content": "I've reviewed the requirements and have some questions about the implementation approach.",
    "internal": false
  }
}

Get Ticket Details

{
  "name": "get-ticket-details",
  "arguments": {
    "ticketReference": "TEL037"
  }
}

Mark Ticket as Blocked

{
  "name": "mark-ticket-as-blocked",
  "arguments": {
    "ticketReference": "TEL037",
    "reason": "Waiting for external API documentation"
  }
}

Get Next Task

{
  "name": "get-next-task",
  "arguments": {
    "applicationSlug": "myapp"
  }
}

Update Action Item Status

{
  "name": "update-action-item",
  "arguments": {
    "ticketReference": "TEL037",
    "actionPoint": "Review database schema",
    "status": "COMPLETED"
  }
}

Error Handling

The server will return appropriate error messages for:

• Authentication failures (invalid PAT token)
• Missing required parameters
• Ticket not found
• Network connectivity issues
• Telos API errors

Development

Building

npm run build

Publishing

npm whoami
npm login
npm version patch|minor|major
npm publish --access public

Advanced Features

For full access to all Telos MCP features, you can also connect directly to your Telos instance:

{
  "mcpServers": {
    "telos-direct": {
      "type": "sse",
      "url": "https://go.telosready.com/mcp?apiKey=pat_your_token_here"
    }
  }
}

This provides access to advanced features like:

• AI-powered question answering
• Real-time ticket updates
• Advanced action item management

Support

If you encounter issues:

1. Check that your PAT token is valid and not expired
2. Verify you have access to the applications/tickets you're trying to access
3. Ensure your Telos instance URL is correct
4. Check the MCP client logs for detailed error messages

License

ISC