Skip to main content
Glama

decimalai-mcp

Part of DecimalAI. Most users want the Python SDK → decimal-labs/decimalai-python.

MCP server for the DecimalAI skills registry — the registry that ranks agent skills by measured effectiveness (verified A/B benchmarks, live pass rates, AI rater scores), not download counts.

PyPI Downloads CI Python License

Gives any MCP client (Claude Desktop, Claude Code, Cursor, …) three read-only tools:

Tool

What it does

search_skills(query, category?, sort?, limit?)

Hybrid keyword/semantic search over the public registry

get_skill(slug)

Full record: trust & safety-scan status, verified benchmark lift, SkillScore, ratings, SKILL.md body, and how to install it (decimalai skills add <slug>, the folder it lands in, and the Claude Code --plugin-dir line)

get_leaderboard(sort?, category?, window_days?, limit?)

Ranked leaderboard: skill_score, biggest_improvement, efficiency, top_rated

No API key required — all three tools read public registry endpoints. If you set DECIMAL_API_KEY (from app.decimal.ai/settings), the same tools additionally show which skills your org has already installed (installed_as).

Install

pip install decimalai-mcp
# or, no install needed at config time:
uvx decimalai-mcp

Requires Python 3.10+.

Related MCP server: skillforge

Claude Code

claude mcp add decimalai -- uvx decimalai-mcp
# with an API key:
claude mcp add decimalai -e DECIMAL_API_KEY=dai_sk_... -- uvx decimalai-mcp

Claude Desktop

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "decimalai": {
      "command": "uvx",
      "args": ["decimalai-mcp"],
      "env": {
        "DECIMAL_API_KEY": "dai_sk_optional"
      }
    }
  }
}

Omit the env block entirely for anonymous read-only access.

Configuration

Env var

Default

Purpose

DECIMAL_API_KEY

(unset)

Optional. Unlocks per-org enrichment (e.g. installed_as) on the same public endpoints.

DECIMAL_API_URL

https://api.decimal.ai

Point at a self-hosted / local backend.

Why no check_manifest_impact tool?

The manifest-impact endpoint (POST /api/v1/regression-check) is authenticated on the platform — it analyzes your org's production traces against a candidate manifest, so there is no public variant to expose. This server is deliberately a read-only, key-optional public-registry surface. If demand shows up, an authed check_manifest_impact (requiring DECIMAL_API_KEY) is a natural v0.2 addition; the regression-check GitHub Action covers the CI use-case today.

Endpoints used (all public)

  • GET /api/v1/registry/skills — browse/search

  • GET /api/v1/registry/skills/{slug} — detail

  • GET /api/v1/registry/leaderboard — ranked leaderboard (category filtering falls back to the browse endpoint's documented view=ranks mode, because the leaderboard endpoint is uncategorized)

Development

pip install -e ".[dev]"
pytest              # all HTTP mocked; no network
python -m decimalai_mcp.server   # run over stdio

Run pytest yourself before opening a PR. CI also asserts that the pinned mcp<2 still provides FastMCP, which the mocked tests do not cover — run that one too:

python -c "from mcp.server.fastmcp import FastMCP; import decimalai_mcp.server"

Releases are cut from a published GitHub Release — see RELEASING.md for the gates a change has to pass and the version strings that must move together.

License

MIT

Available Tools

3 tools
get_leaderboardA

Ranked skills leaderboard.

Args: sort: skill_score | biggest_improvement | efficiency | top_rated. category: Optional category filter (uses the registry's ranked browse view — the dedicated leaderboard endpoint is uncategorized). window_days: Ranking window in days (1-3650; ignored for skill_score). limit: Max entries (1-50).

Inputs: sort, limit, category, window_days. Returns: result

get_skillA

Get one skill's full record: trust/safety-scan status, verified benchmark evidence (lift vs no-skill baseline), SkillScore, ratings, the SKILL.md body, and how to install it: its install name (the folder it installs into) and the decimalai skills add <ref> command that writes that folder. The install part is left out for a skill that is blocked or withheld, or whose safety scan is flagged and awaiting review.

Args: slug: The skill's url_slug from search results — NOT its name. A registry name may be namespaced (owner/skill), and a slash cannot survive a single URL path segment, so a namespaced name 404s here. url_slug is the slash-free identifier minted for exactly this (owner/skill -> owner-skill); for a plain un-namespaced name the two are identical. The skill's UUID id also works.

Inputs: slug (required). Returns: result

search_skillsA

Search the public DecimalAI skills registry.

Args: query: Keyword or natural-language query (hybrid keyword/semantic search). category: Optional category filter (e.g. "retrieval", "code-review"). sort: recommended (SkillScore v2, default) | lift | popular | top_rated | efficiency | rating | recent. limit: Max results (1-50).

Inputs: query (required), sort, limit, category. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv0.1.3
    • First observedget_leaderboard
    • First observedget_skill
    • First observedsearch_skills

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a clearly distinct action on the registry: fetch one skill by slug, retrieve a ranked leaderboard, and search the registry. Descriptions reinforce the boundaries (e.g. get_skill's note that slug is not the name), so an agent will not misselect among them.

Naming Consistency5/5

All three names follow a clean verb_noun pattern (get_skill, get_leaderboard, search_skills) using snake_case consistently. The convention is predictable and readable.

Tool Count4/5

Three tools is a small but coherent set for a read-only skills registry: discover (search), inspect (get), and rank (leaderboard). It is slightly thin — no category-listing or comparison tool — but each tool earns its place.

Completeness4/5

The surface covers the core discovery workflow: search, detail lookup (including install instructions), and ranked browsing. Minor gaps exist (no category enumeration, version history, or cross-skill comparison), but agents can work around them within the stated read-only scope.

Maintenance

ActivityMaintained
ResponsivenessOutdated data

Related MCP Connectors

Related MCP Servers