loading…
Search for a command to run...
loading…
Enables natural language management of Latitude.sh infrastructure, allowing users to list, create, and delete servers, projects, and SSH keys through MCP-compat
Enables natural language management of Latitude.sh infrastructure, allowing users to list, create, and delete servers, projects, and SSH keys through MCP-compatible clients.
Model Context Protocol (MCP) server for the Latitude.sh API
The Latitude.sh MCP Server exposes your Latitude.sh REST API as an AI-ready interface, allowing developer tools and assistants to list, create, and manage your infrastructure resources programmatically.
Use natural language to:
🪶 Prerequisite: You’ll need a Latitude.sh API Key.
Install the MCP server as a Desktop Extension using the pre-built mcp-server.dxt file:
Simply drag and drop the mcp-server.dxt file onto Claude Desktop to install the extension.
The DXT package includes the MCP server and all necessary configuration. Once installed, the server will be available without additional setup.
[!NOTE] DXT (Desktop Extensions) provide a streamlined way to package and distribute MCP servers. Learn more about Desktop Extensions.
{
"mcpServers": {
"Latitudesh": {
"command": "npx",
"args": [
"latitudesh",
"start",
"--bearer",
"<YOUR_API_KEY>"
]
}
}
}
Note: Replace YOUR_LATITUDE_API_TOKEN with your actual Latitude.sh bearer token.
claude mcp add latitudesh npx latitudesh start -- --bearer YOUR_LATITUDE_API_TOKEN
Note: Replace YOUR_LATITUDE_API_TOKEN with your actual Latitude.sh bearer token.
Add the MCP server with the Codex CLI:
codex mcp add Latitudesh -- npx latitudesh start --bearer YOUR_LATITUDE_API_TOKEN
Or add it directly to ~/.codex/config.toml:
[mcp_servers.Latitudesh]
command = "npx"
args = ["latitudesh", "start", "--bearer", "YOUR_LATITUDE_API_TOKEN"]
Verify it is configured:
codex mcp list
Note: Replace YOUR_LATITUDE_API_TOKEN with your actual Latitude.sh bearer token.
Refer to Official Windsurf documentation for latest information
Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account)View raw config to open up the mcp configuration file.{
"mcpServers": {
"Latitudesh": {
"command": "npx",
"args": [
"latitudesh",
"start",
"--bearer",
"<YOUR_API_KEY>"
]
}
}
}
Refer to Official VS Code documentation for latest information
MCP: Open User Configuration. This should open mcp.json file{
"mcpServers": {
"Latitudesh": {
"command": "npx",
"args": [
"latitudesh",
"start",
"--bearer",
"<YOUR_API_KEY>"
]
}
}
}
You need to do the following
SettingsDeveloper tab (on the left hand side)Edit Config
Paste the following config in the configuration{
"mcpServers": {
"Latitudesh": {
"command": "npx",
"args": [
"latitudesh",
"start",
"--bearer",
"<YOUR_API_KEY>"
]
}
}
}
Note: Replace YOUR_LATITUDE_API_TOKEN with your actual Latitude.sh bearer token.
Refer to Official VS Code documentation for latest information
Cmd+Shift+P / Ctrl+Shift+P)MCP: Open User Configuration to open the mcp.json file{
"servers": {
"Latitudesh": {
"type": "stdio",
"command": "npx",
"args": [
"latitudesh",
"start",
"--bearer",
"YOUR_LATITUDE_API_TOKEN"
]
}
}
}
Cmd+Alt+I / Ctrl+Alt+I) and enable Agent modeNote: Replace YOUR_LATITUDE_API_TOKEN with your actual Latitude.sh bearer token.
Tips for using with VS Code:
Settings → Developer tabEdit Config{
"mcpServers": {
"Latitudesh": {
"command": "npx",
"args": [
"latitudesh",
"start",
"--bearer",
"YOUR_LATITUDE_API_TOKEN"
]
}
}
}
Note: Replace YOUR_LATITUDE_API_TOKEN with your actual Latitude.sh bearer token.
To start the MCP server directly:
npx latitudesh start --bearer YOUR_LATITUDE_API_TOKEN
Optional flags:
--server-index <0|1> - Select server (0=https://api.latitude.sh, 1=http://api.latitude.sh) [default: 0]--latitude-api-key <key> - API key for URL templating--log-level <level> - Log level (debug|warning|info|error) [default: info]For a full list of server arguments:
npx latitudesh --help
Run locally without a published npm package:
npm installnpm run buildnode ./bin/mcp-server.js start --bearer <YOUR_API_KEY>To use this local version with MCP Clients, you'll need to add the following config:
{
"mcpServers": {
"Latitudesh": {
"command": "node",
"args": [
"/absolute/path/to/latitudesh-mcp/bin/mcp-server.js",
"start",
"--bearer",
"<YOUR_API_KEY>"
]
}
}
}
Use the official MCP Inspector:
npx @modelcontextprotocol/inspector node ./bin/mcp-server.js start --bearer <YOUR_API_KEY>
This opens an interactive UI at http://localhost:6274.
While we welcome contributions, most of this code is auto-generated. Manual edits to generated files will be overwritten on regeneration.
If you'd like to suggest improvements:
Latitude.sh API: The Latitude.sh API is a RESTful API to manage your Latitude.sh account. It allows you to perform the same actions as the Latitude.sh dashboard.
Install the MCP server as a Desktop Extension using the pre-built mcp-server.mcpb file:
Simply drag and drop the mcp-server.mcpb file onto Claude Desktop to install the extension.
The MCP bundle package includes the MCP server and all necessary configuration. Once installed, the server will be available without additional setup.
[!NOTE] MCP bundles provide a streamlined way to package and distribute MCP servers. Learn more about Desktop Extensions.
Or manually:
{
"command": "npx",
"args": [
"latitudesh",
"start",
"--server-index",
"0",
"--latitude-api-key",
"<insert your api key here>",
"--bearer",
""
]
}
claude mcp add Latitudesh -- npx -y latitudesh start --server-index 0 --latitude-api-key <insert your api key here> --bearer
gemini mcp add Latitudesh -- npx -y latitudesh start --server-index 0 --latitude-api-key <insert your api key here> --bearer
Add the MCP server with the Codex CLI:
codex mcp add Latitudesh -- npx -y latitudesh start --server-index 0 --latitude-api-key <insert your api key here> --bearer <insert your bearer token here>
Or add it directly to ~/.codex/config.toml:
[mcp_servers.Latitudesh]
command = "npx"
args = ["-y", "latitudesh", "start", "--server-index", "0", "--latitude-api-key", "<insert your api key here>", "--bearer", "<insert your bearer token here>"]
Verify it is configured:
codex mcp list
Refer to Official Windsurf documentation for latest information
Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account)View raw config to open up the mcp configuration file.{
"command": "npx",
"args": [
"latitudesh",
"start",
"--server-index",
"0",
"--latitude-api-key",
"<insert your api key here>",
"--bearer",
""
]
}
Or manually:
Refer to Official VS Code documentation for latest information
MCP: Open User Configuration. This should open mcp.json file{
"command": "npx",
"args": [
"latitudesh",
"start",
"--server-index",
"0",
"--latitude-api-key",
"<insert your api key here>",
"--bearer",
""
]
}
npx latitudesh start --server-index 0 --latitude-api-key <insert your api key here> --bearer
For a full list of server arguments, run:
npx latitudesh --help
MCP servers with many tools can bloat LLM context windows, leading to increased token usage and tool confusion. Dynamic mode solves this by exposing only a small set of meta-tools that let agents progressively discover and invoke tools on demand.
To enable dynamic mode, pass the --mode dynamic flag when starting your server:
{
"mcpServers": {
"Latitudesh": {
"command": "npx",
"args": ["latitudesh", "start", "--mode", "dynamic"],
// ... other server arguments
}
}
}
In dynamic mode, the server registers only the following meta-tools instead of every individual tool:
list_tools: Lists all available tools with their names and descriptions.describe_tool: Returns the input schema for one or more tools by name.execute_tool: Executes a tool by name with the provided input parameters.This approach significantly reduces the number of tokens sent to the LLM on each request, which is especially useful for servers with a large number of tools.
Выполни в терминале:
claude mcp add latitude-sh-mcp-server -- npx Не уверен что выбрать?
Найди свой стек за 60 секунд
Автор?
Embed-бейдж для README
Похожее
Все в категории development