🚀 Latitude MCP Server 🚀

🚀 Latitude MCP Server 🚀

Stop copy-pasting prompts. Start managing them like a pro.

The complete MCP server for Latitude.so prompt management. Create projects, version prompts, push from local files, run AI conversations — all from your AI assistant or CLI.

  •  

latitude-mcp-server gives your AI assistant superpowers for managing prompts on Latitude.so. Instead of switching between your IDE, Latitude dashboard, and AI chat, your AI can now create projects, version prompts, push content from local files, and even run prompts directly.

How it works:

• You: "Push my local prompt file to Latitude draft"
• AI: Reads file, extracts prompt path from filename, pushes to your project
• You: "Now run it with these parameters"
• AI: Executes prompt, streams response, maintains conversation
• Result: Full prompt lifecycle without leaving your IDE

💥 Why This Beats Manual Management

Managing prompts manually is a context-switching nightmare. This MCP server makes traditional workflows look ancient.

We're not just wrapping an API. We're enabling AI-native prompt development with file-based workflows, automatic path derivation, and streaming execution.

🚀 Get Started in 60 Seconds

1. Get Your API Key

1. Go to app.latitude.so/settings
2. Create or copy your API key
3. That's it — one key, all features unlocked

2. Configure Your MCP Client

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "latitude": {
      "command": "npx",
      "args": ["latitude-mcp-server"],
      "env": {
        "LATITUDE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Claude Code (CLI)

One command setup:

claude mcp add latitude npx \
  --scope user \
  --env LATITUDE_API_KEY=your-api-key-here \
  -- latitude-mcp-server

Or manually add to ~/.claude.json:

{
  "mcpServers": {
    "latitude": {
      "command": "npx",
      "args": ["latitude-mcp-server"],
      "env": {
        "LATITUDE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Cursor/Windsurf

Add to .cursor/mcp.json or MCP settings:

{
  "mcpServers": {
    "latitude": {
      "command": "npx",
      "args": ["latitude-mcp-server"],
      "env": {
        "LATITUDE_API_KEY": "your-api-key-here"
      }
    }
  }
}

✨ Pro Tip: The server outputs in TOON format by default — a token-efficient notation that uses 30-60% fewer tokens than JSON, keeping your LLM context lean.

✨ Feature Breakdown

🛠️ Tool Reference

This server provides 18 MCP tools covering the complete Latitude API plus built-in documentation.

📚 Documentation Tools (AI Self-Learning)

The server includes self-documenting capabilities so AI agents can learn PromptL syntax on-demand without external lookups.

latitude_help

Get complete server overview — all tools, documentation topics, and quick start workflow.

// No parameters required
{}

Returns: Server overview with tool list, doc topics, and suggested next actions.

AI agents should call this first to understand available capabilities.

latitude_get_docs

Get comprehensive PromptL documentation for a specific topic.

Available Topics:

{
  "topic": "variables"
}

Returns: Comprehensive documentation with syntax, examples, best practices, and next steps.

Writing PromptL-Compliant Prompts

AI agents can use these tools to write valid PromptL prompts:

1. latitude_help                           → Understand server capabilities
2. latitude_get_docs({ topic: "structure" }) → Learn basic prompt structure
3. latitude_get_docs({ topic: "variables" }) → Learn {{ }} syntax
4. latitude_push_prompt                     → Push your prompt
5. latitude_run_prompt                      → Test execution

Example learning flow for writing a prompt with conditionals:

AI: latitude_get_docs({ topic: "structure" })
   → Learns: Config section (---), message tags (<user>, <assistant>)

AI: latitude_get_docs({ topic: "conditionals" })
   → Learns: {{ if }}, {{ else }}, {{ endif }} syntax

AI: Now writes valid PromptL:
   ---
   provider: OpenAI
   model: gpt-4o
   ---
   {{ if user.isPremium }}
     You have access to all features!
   {{ else }}
     Upgrade for premium features.
   {{ endif }}
   
   <user>{{ question }}</user>

Project Tools

latitude_list_projects

List all projects in your Latitude workspace.

// No parameters required
{}

Returns: Array of projects with id, name, createdAt, updatedAt

latitude_create_project

Create a new project.

{
  "name": "My Awesome Prompts"
}

Version Tools

latitude_list_versions

List all versions (commits) for a project.

{
  "projectId": "27756"
}

latitude_get_version

Get details for a specific version.

latitude_create_version

Create a new draft version (branch).

{
  "projectId": "27756",
  "name": "feature-new-tone"
}

latitude_publish_version

Publish a draft version to make it live.

Prompt Tools

latitude_list_prompts

List all prompts in a version.

latitude_get_prompt

Get a specific prompt by path.

{
  "projectId": "27756",
  "path": "onboarding/welcome",
  "versionUuid": "79b52596-7941-4ed3-82cf-23e13fa170db"
}

latitude_push_prompt

Push prompt content to a draft version.

{
  "projectId": "27756",
  "versionUuid": "79b52596-7941-4ed3-82cf-23e13fa170db",
  "path": "greeting",
  "content": "---\nprovider: openai\nmodel: gpt-4o-mini\n---\nHello {{name}}! Welcome to our service."
}

latitude_push_prompt_from_file ⭐

Push a prompt directly from a local file. This is the killer feature for IDE workflows.

Auto-derivation: If you push /path/to/my-prompt.md, it automatically becomes my-prompt in Latitude.

{
  "projectId": "27756",
  "versionUuid": "79b52596-7941-4ed3-82cf-23e13fa170db",
  "filePath": "/Users/you/prompts/welcome-message.md"
}

Supported extensions: .md, .promptl, .txt

Execution Tools

latitude_run_prompt

Execute a prompt and get AI response.

{
  "projectId": "27756",
  "path": "greeting",
  "parameters": { "name": "World" },
  "stream": true
}

latitude_chat

Continue an existing conversation.

latitude_get_conversation

Get full conversation history.

Operations Tools

latitude_list_logs

Get execution logs for a prompt.

latitude_create_log

Create a log entry for external executions.

latitude_trigger_evaluation

Trigger an evaluation run for a prompt.

📚 Resource Templates

Access Latitude data via MCP resources (read-only):

💻 CLI Reference

The server also works as a standalone CLI tool:

# Set your API key
export LATITUDE_API_KEY="your-key"

# Or use inline
LATITUDE_API_KEY="your-key" latitude-mcp projects list

Commands

# Projects
latitude-mcp projects list
latitude-mcp projects create "My Project"

# Versions
latitude-mcp versions list <projectId>
latitude-mcp versions create <projectId> "Draft Name"

# Prompts
latitude-mcp prompts list <projectId> -v <versionUuid>
latitude-mcp prompts get <projectId> <path> -v <versionUuid>

# Push (inline content)
latitude-mcp push <projectId> <versionUuid> <promptPath> --content "---\nprovider: openai\n---\nHello!"

# Push (from file) ⭐
latitude-mcp push <projectId> <versionUuid> --file /path/to/prompt.md

# Run
latitude-mcp run <projectId> <path> -v <versionUuid> -p '{"name": "World"}'

# Chat
latitude-mcp chat <conversationUuid> -m "Follow up question"

Options

🔥 Recommended Workflows

Local Development Flow

1. Write prompt in your IDE: /prompts/my-feature.md
2. AI: "Push this to my Latitude draft"
   → latitude_push_prompt_from_file
3. AI: "Run it with test parameters"
   → latitude_run_prompt
4. Iterate on content locally
5. AI: "Push the updated version"
6. AI: "Publish to live"
   → latitude_publish_version

Prompt Audit Flow

1. AI: "List all my Latitude projects"
   → latitude_list_projects
2. AI: "Show me all prompts in project 27756"
   → latitude_list_prompts
3. AI: "Get the content of the onboarding prompt"
   → latitude_get_prompt
4. AI: "Check the execution logs"
   → latitude_list_logs

Conversation Testing Flow

1. AI: "Run the support-bot prompt"
   → latitude_run_prompt (returns conversationUuid)
2. AI: "Continue with: What about refunds?"
   → latitude_chat
3. AI: "Show the full conversation"
   → latitude_get_conversation

⚙️ Environment Variables

Skip projectId with Default Project

Set LATITUDE_PROJECT_ID to avoid specifying projectId in every tool call:

{
  "mcpServers": {
    "latitude": {
      "command": "npx",
      "args": ["latitude-mcp-server"],
      "env": {
        "LATITUDE_API_KEY": "your-api-key",
        "LATITUDE_PROJECT_ID": "27756"
      }
    }
  }
}

When set, all tools that require projectId will use this default. You can still override per-call.

🔥 Common Issues & Quick Fixes

🛠️ Development

# Clone
git clone https://github.com/yigitkonur/latitude-mcp-server.git
cd latitude-mcp-server

# Install
npm install

# Build
npm run build

# Test
npm test

# Run locally
LATITUDE_API_KEY=your-key node dist/index.js projects list