pokemon-battle-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.0
Disambiguation5/5
Each tool has a clearly distinct purpose: meta snapshot, single Pokemon options, stat calculation, damage calculation, and three specific optimize tools for offensive, survival, and speed spreads, plus speed tiers. The descriptions also include cross-references that further clarify when to use each tool.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using lowercase snake_case (get_meta_snapshot, calculate_stats, check_damage_matchup, optimize_offensive_spread). The actions are descriptive and the pattern is uniform.
Tool Count5/5
8 tools is well-scoped for a Pokemon battle assistant, covering meta information, stat calculation, damage calculation, and optimization. Each tool serves a distinct function without unnecessary redundancy.
Completeness5/5
The tool set covers the full workflow of building Pokemon sets: gathering meta information, obtaining specific Pokemon options, calculating stats, checking damage, and optimizing offensive, defensive, and speed spreads. There are no obvious dead ends or missing operations for the stated purpose.
Average 3.7/5 across 8 of 8 tools scored. Lowest: 2.7/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 2 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.
MCP servers without a LICENSE cannot be installed.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the optimization goal but omits details such as damage formula assumptions, how 'minimum' is calculated (e.g., SP budget constraints), failure modes when no spread achieves the target, or whether it accounts for moves/abilities. The mention of get_pokemon_options hints at cross-tool dependency but does not disclose overall behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences and front-loaded with the primary purpose. No filler words; every sentence contributes a distinct point (goal and canonical-naming guidance).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex tool with 8 parameters and a nested schema, the description is too minimal. It lacks mention of expected usage scenarios, relationship to other optimizer tools, and the meaning of the output. Although an output schema exists (reducing the need to explain return values), the description still provides insufficient context for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not compensate by explaining key parameters like targetDamageRatio, spBudget, allowedNatures, or offensiveStat. The only indirect reference is 'attacking SP and nature,' which duplicates the tool's title. The rich input schema descriptions carry all semantics, so the description adds no value for parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Find the minimum attacking SP and nature needed to reach a target damage ratio.' It distinguishes from sibling optimization tools by specifying 'attacking' as the optimization target, but does not explicitly name alternative tools for survival/speed spreads.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Only a tangential usage note is provided: 'Use canonical current-format formes from get_pokemon_options when the user asks about a Mega/forme.' This addresses input naming for specific cases but does not explain when to choose this tool over sibling optimization tools (e.g., optimize_survival_spread).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the tool returns sorted data and uses a current meta seed/source, which implies a read-only operation. However, it lacks details about side effects, error handling, or how the seed is determined, so transparency is limited.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that is front-loaded with the core functionality. Every word earns its place, with no unnecessary filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has moderate complexity due to the filters parameter, and although an output schema exists, the description is too brief to explain what 'speed benchmarks' means, how the meta seed/source is selected, or how the filters interact. This is inadequate for an agent to fully understand when and how to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 67%, with descriptions for limit and includeModifiers, but the filters parameter is undocumented. The description adds no parameter information at all, failing to clarify the complex filters structure. This leaves a significant gap in understanding the tool's inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns sorted speed benchmarks from the current meta seed/source, using a specific verb and resource. It is relatively specific but does not explicitly differentiate itself from sibling tools like optimize_speed_spread, which could also involve speed benchmarks.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It only states what it does, without mentioning when it is appropriate or when to choose a sibling tool like get_meta_snapshot or optimize_speed_spread.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It discloses that the tool optimizes only HP and defensive stats, and it specifies the canonical-forme requirement, which is useful behavioral context. However, it does not state whether the operation is read-only, what the output contains, or assumptions about other stats, leaving gaps in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, each informative: the first states the core optimization goal, and the second gives a critical input-format guideline. There is no redundancy or filler, making it exceptionally concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema, the tool has 8 parameters with deep nesting. The description covers only the basic optimization goal and the forme-canonicalization rule, leaving many optional parameters and usage nuances undocumented. For a tool of this complexity, the description is not complete enough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for parameter meaning. It gives only implicit hints: 'HP plus defense/special-defense' maps to defender SP stats and the defensiveStat parameter, and 'specified attack' maps to move. It does not explain spBudget, survivalThreshold, context, or allowedNatures, so the description is insufficient.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Find the minimum HP plus defense/special-defense SP allocation that survives a specified attack.' This uses a specific verb ('Find') and a precise resource (defensive SP allocation), making it distinct from offensive or speed optimization tools. The additional note about canonical formes further clarifies its scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context: it is for defensive survival optimization, and it gives a concrete usage instruction to use canonical formes from get_pokemon_options for Mega/forme requests. However, it does not explicitly mention alternatives like optimize_offensive_spread or state when not to use this tool, so it does not fully meet the 'when/when-not' standard.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description itself only indicates a retrieval operation, which is non-destructive and safe. However, it does not disclose behaviors such as input normalizations (though schema mentions corrections are reported), default format handling, or any external dependencies, leaving some transparency gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence listing key outputs without wasted words. It uses consistent comma-separated items, making it easy to scan and understand.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity and presence of an output schema, the description adequately lists return content and scopes to one Pokémon. However, it omits guidance on parameter interactions (e.g., default include behavior) and does not differentiate from siblings, making it slightly incomplete for full contextual navigation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%, with descriptions for 'pokemon' and 'format' but not for the two boolean flags. The description's mention of 'optional teammates/counters' hints at includeTeammates/includeCounters, but it does not explicitly map parameters, so semantics for the booleans remain partially inferred.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves 'common sets, moves, items, abilities, spreads, and optional teammates/counters' for a single Pokémon, using a specific verb and resource. This distinguishes it from siblings like calculate_stats or get_speed_tiers, which focus on calculations and speed tiers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when teambuilding needs suggested sets/options for a Pokémon, but it does not explicitly contrast with sibling tools or state when not to use it. For example, it does not mention using calculate_stats for damage calculations instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses a key behavioral trait ('resolves unambiguous current-meta base-forme mistakes') and the core calculation behavior, but does not mention safety, side effects, or limitations (e.g., how it simulates speed modifiers). It's adequate but not exhaustive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core purpose, and contains no redundant or filler text. Every clause earns its place, including the sibling-tool guidance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description captures the essential purpose and a critical prerequisite, but for a complex tool with nested schema and a separate output schema, it leaves out important context such as how the target should be specified or what the result contains. The output schema mitigates the need to explain return values, but the description still feels minimal for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% at the top level, and the description does not compensate. It only implies that 'Speed SP' and 'nature' are relevant inputs and references 'target' generically, but does not explain relation, spBudget, allowedNatures, or context. This is a significant gap for a tool with nested objects and 6 parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Find the minimum Speed SP and nature') with a clear resource ('Speed SP') and outcome ('outspeed, speed tie, or underspeed a target'). It effectively distinguishes from sibling tools like optimize_offensive_spread and optimize_survival_spread by focusing on speed-related optimization.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises using get_pokemon_options first for current-format Mega/forme requests, providing a clear when-to-use alternative. The note about resolving base-forme mistakes gives additional context, though it does not explicitly mention when not to use this tool or compare to other speed-focused siblings like get_speed_tiers.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses that the tool returns popular meta data, but it does not mention data source, freshness, or whether limit applies per category. The output schema covers return structure, so the description does not need to explain that, but additional behavioral details are absent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no redundant words. It efficiently lists the key elements returned.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description, combined with the output schema and complete parameter schemas, gives sufficient context for an agent to understand the tool's purpose and return. Minor gap: no mention of how limit affects categories or whether data is cached/live.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with each parameter having a description and default. The tool description adds no extra parameter-level meaning beyond referencing 'current format,' which maps to the format parameter. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves popular Pokémon, moves, items, abilities, and SP spreads for the current format. The content and verb 'Get' distinguish it from sibling calculation and optimization tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context that this is for current format meta data, implying it should be used when snapshot popularity data is needed. It does not explicitly exclude calculation tools, but the nature of the output is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the transparency burden. It discloses two important behavioral traits: 1) it includes stage-modified stats only when battle state is present (context-dependent), and 2) it resolves unambiguous current-meta base-forme mistakes server-side. These are non-obvious and useful. It does not mention side effects or auth, but as a calculation tool that is unlikely. The correction behavior is well-highlighted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, each earning its place. The first presents the core function, the second provides guidance on when to use alternatives and discloses correction behavior. There is no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has a complex nested schema with two parameters, and an output schema is provided. The description is sufficient for understanding the primary use case and mentions the key context-dependency (stage-modified stats). It could be more complete by explicitly mentioning that corrections are reported via inputCorrections (a behavioral detail in the schema), but overall it covers the essential context for an agent to select and invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description names the key inputs 'species, nature, and SP', which maps to pokemon.name, pokemon.nature, and pokemon.sp. It also hints that battle state (likely context) affects stage-modified stats. However, it does not explain the structure of the context object or the exact SP format, leaving those to the schema. Given the context signal of 0% schema description coverage, the description should compensate more, but it adds some value beyond parameter names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb+resource: 'Calculate level-50 Pokémon Champions stats from species, nature, and SP', and further specifies that stage-modified stats are included when battle state is present. It clearly distinguishes from sibling tools like get_pokemon_options by explicitly mentioning that for current-format builds/Mega/formes, get_pokemon_options should be preferred.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit guidance on when to prefer get_pokemon_options ('For user requests about current-format builds or Mega/formes, prefer get_pokemon_options first') and explains the correction behavior. However, it does not contrast with other siblings like optimization tools (e.g., optimize_offensive_spread) or check_damage_matchup, so it lacks full coverage of when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses key behavior: SP conversion to standard EVs and that item legality is not validated. It doesn't mention side effects or error handling, but this is a pure calculation, and output schema covers return values. The description adds value beyond the schema by explaining the conversion.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, with two sentences: the first states the purpose, the second gives a usage guideline and a caveat. No redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the core purpose, a suggested workflow, and a legality caveat. Given the rich input schema (which documents parameters and nested objects) and the presence of an output schema, this is adequate. It could mention format or that it's read-only, but those are less critical.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool description does not enumerate parameters, but it clarifies that 'Pokémon Champions SP' is used and that item choices are accepted as provided, which gives context for the `sp` and `item` fields. The move and context parameters are not addressed. Since the input schema itself has detailed descriptions for each property, the base coverage is decent, but the tool description only partially compensates given the 0% schema_description_coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool performs a forward damage calculation with a specific EV conversion, using a verb ('Run') and resource ('damage calculation'). It distinguishes from siblings like calculate_stats by focusing on damage matchup, and the name reinforces it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly instructs to call get_pokemon_options first for build questions and use canonical formes/builds, providing an alternative workflow. It also notes item choices are accepted as provided and not legality-validated, giving context. However, it doesn't explicitly state when not to use this tool versus other damage/stat tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![pokemon-battle-mcp MCP server](https://glama.ai/mcp/servers/hahastudio/pokemon-battle-mcp/badges/card.svg)](https://glama.ai/mcp/servers/hahastudio/pokemon-battle-mcp)

Score Badge

Copy to your README.md:

[![pokemon-battle-mcp MCP server](https://glama.ai/mcp/servers/hahastudio/pokemon-battle-mcp/badges/score.svg)](https://glama.ai/mcp/servers/hahastudio/pokemon-battle-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hahastudio/pokemon-battle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server