Skip to main content
Glama
rkorablin

confluence-http-api-mcp

by rkorablin

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CONFLUENCE_PATNoAlias for CONFLUENCE_TOKEN
CONFLUENCE_URLYesBase URL, e.g. https://wiki.it-aces.com
CONFLUENCE_TOKENNoPersonal Access Token sent as Authorization: Bearer

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
confluence_searchA

Search Confluence pages with CQL. Examples: space=GAR AND type=page, space=GAR AND title ~ "API", text ~ "address search" AND space=GAR. Returns titles, ids, excerpts.

confluence_get_pageA

Get a Confluence page by numeric content id. Returns title, space, ancestors and plain-text body.

confluence_get_page_by_titleA

Get a page by space key and exact title (first match).

confluence_list_spacesA

List Confluence spaces accessible with the token.

confluence_get_page_childrenA

List child pages under a parent page (table of contents / doc tree).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct resource or access pattern: search uses CQL, get_page uses numeric ID, get_page_by_title uses space+title, list_spaces enumerates spaces, and get_page_children navigates hierarchy. No two tools overlap in purpose.

Naming Consistency5/5

All tools use a consistent 'confluence_' prefix followed by a verb_noun pattern. The two get_page variants are differentiated by suffix 'by_title', maintaining clarity.

Tool Count5/5

Five tools is well-scoped for a read-only Confluence integration; each tool serves a distinct function without redundancy or excessive minimalism.

Completeness4/5

The core read operations are present: search, get by ID, get by title, list spaces, and list children. However, there are no mutation endpoints and no space-level detail tool, leaving minor gaps for a full API surface.

Maintenance

ActivityInactive
ResponsivenessNo issues