Skip to main content
Glama
Aiden-Kwak

apic-docs-mcp

by Aiden-Kwak

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_apic_docsA

Search IBM API Connect 12.1.0 documentation. Returns matching topics with titles, snippets, and URLs.

read_apic_docA

Read a specific IBM API Connect documentation page and return its content as Markdown. Use the 'href' from search results or TOC.

get_apic_tocA

Get the table of contents for IBM API Connect 12.1.0 documentation. Shows the full document structure with sections and topics.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clear, non-overlapping purpose: searching documentation, reading a specific page, and retrieving the table of contents. An agent can easily select the right tool based on the task.

Naming Consistency4/5

All tool names follow a consistent verb_noun pattern: search_, read_, get_. There is a minor inconsistency between 'apic_docs' and 'apic_doc' (plural vs singular), but this does not create confusion.

Tool Count5/5

Three tools is a focused, well-scoped set for a documentation server. Each tool serves a distinct and necessary function without redundancy or bloat.

Completeness5/5

The toolkit covers the full documentation workflow: discovering topics via search, navigating structure via TOC, and retrieving full content via read. There are no obvious gaps for a docs-only MCP server.

Maintenance

ActivityInactive
ResponsivenessNo issues