MCP Server

minware MCP Server

The minware MCP (Model Context Protocol) server lets you connect AI coding tools directly to your minware analytics data. Once configured, your AI assistant can query dashboards, retrieve engineering metrics, and answer questions about your team's performance — without leaving your development workflow.

The server is available at:

https://app.minware.com/api/mcp

There are two ways to connect:

Sign in with your minware account. Tools that support signing in to MCP servers (Claude, Claude Code, ChatGPT and Codex) open a minware login when you add the server. Any member of a minware org can connect this way.
Use an API key. Tools that send a fixed bearer token connect with an API key, which only an Org Owner can create.

Add the server URL in your tool following its own instructions for remote MCP servers:

Claude (web, Desktop and mobile)
Claude Code
ChatGPT
Codex

The tool opens a minware sign-in in your browser. After you sign in:

If your account belongs to more than one org, choose the org the tool should read reports from. If it belongs to exactly one, that org is used without asking.
Approve the access request. The tool is granted read access to the org's reports and dashboards, and nothing else.

The connection reads from one org at a time. To switch orgs, disconnect the server in your tool and connect again, then pick the other org. Choosing a different org also changes the org for your other connected tools the next time they refresh their access.

If none of your orgs allows report access for your account, the sign-in ends with a message saying so; ask an org admin to add you, then connect again.

Use an API key

Prerequisites

A minware account with Org Owner permissions
One of the supported AI tools listed below

Step 1: Generate an API Key

In minware, go to Settings > API Keys
Click New API Key
Enter a descriptive name for the key (e.g., Claude Desktop or Cursor)
Click Create
Copy the key immediately — it will not be shown again

Note: API keys carry the permissions of the user who creates them. Only Org Owners can create API keys. Treat your API key like a password — do not share it or commit it to version control.

Step 2: Configure Your AI Tool

The minware MCP server is available at:

https://app.minware.com/api/mcp

Select your AI tool below for setup instructions.

Claude Desktop

Claude Desktop only connects to remote MCP servers added through Settings > Connectors, and that UI authenticates with OAuth — it has no way to send the Authorization: Bearer header minware's API keys require. To use an API key, bridge the connection with the mcp-remote package instead by editing your Claude Desktop configuration file:

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

Add the minware entry to the mcpServers object:

{
  "mcpServers": {
    "minware": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://app.minware.com/api/mcp",
        "--header",
        "Authorization:${MINWARE_API_KEY}"
      ],
      "env": {
        "MINWARE_API_KEY": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Restart Claude Desktop for the changes to take effect.

Claude Code

Run the following command to register the minware MCP server:

claude mcp add --transport http minware https://app.minware.com/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Verify with /mcp in the Claude Code.

Gemini CLI

Add minware to your Gemini CLI settings at ~/.gemini/settings.json:

{
  "mcpServers": {
    "minware": {
      "httpUrl": "https://app.minware.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

For project-level configuration, use .gemini/settings.json in your repository root instead.

Cursor

Open Cursor Settings > MCP, or add minware to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "minware": {
      "url": "https://app.minware.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Restart Cursor after saving.

Codex

Add minware to your Codex configuration at ~/.codex/config.toml. The recommended approach uses an environment variable to keep your API key out of the config file:

[mcp_servers.minware]
url = "https://app.minware.com/api/mcp"
bearer_token_env_var = "MINWARE_API_KEY"

Then export the key in your shell profile (e.g., ~/.zshrc or ~/.bashrc):

export MINWARE_API_KEY=YOUR_API_KEY

Alternatively, you can store the key directly in the config:

[mcp_servers.minware]
url = "https://app.minware.com/api/mcp"
bearer_token = "YOUR_API_KEY"

Example Prompts

Once configured, try prompts like these to explore your engineering data:

Show me the Benchmarks data for the last 30 days. Which metrics need attention?

What was the average cycle time for the backend team last quarter?

Compare sprint performance across teams over the past 3 months.

The assistant will use minware's tools to list teams and dashboards, fetch the relevant data, and provide analysis in natural language.

Try minware today

Start Free Trial View Live Demo