of-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OF_MCP_DB_PATH | No | Path to the SQLite database index (optional, defaults to ./data/of.db) | ./data/of.db |
| ATLASSIAN_EMAIL | No | Atlassian email (optional, currently not needed as Confluence space is public) | |
| ATLASSIAN_API_TOKEN | No | Atlassian API token (optional, currently not needed as Confluence space is public) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search the Open Finance Brasil docs (BM25). Returns compact snippets. Args: query: Natural-language query in Portuguese or English. limit: Max number of hits (default 6, hard-capped at 20). |
| get_pageA | Return the full markdown of a page. Args: page_ref: Confluence page id, exact title, or substring of the title. section: Optional heading text. If provided, only the matching section (and its sub-sections) is returned. |
| list_sectionsA | List pages in the documentation tree. Args: parent_id: If omitted, returns root pages of the OF space. Otherwise returns immediate children of the given page id. |
| answer_questionA | Retrieve the most relevant chunks formatted as RAG context. The MCP itself does NOT call an LLM — it returns the raw context plus citations so the calling assistant can answer using its own context window (saving tokens vs. running a second model here). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: answer_question returns RAG context, get_page retrieves full page markdown, list_sections navigates the doc tree, and search_docs performs keyword search. No overlap in functionality.
All tools follow a consistent verb_noun snake_case pattern (answer_question, get_page, list_sections, search_docs), making it easy to infer their actions.
With 4 tools, the server is well-scoped for documentation retrieval and search. Each tool earns its place, covering essential operations without unnecessary bloat.
The tool set covers the full lifecycle of documentation access: search (search_docs), context retrieval (answer_question), page content (get_page), and navigation (list_sections). No obvious gaps.