Skip to main content
Glama
azamlerc

confluence-mcp-server

by azamlerc
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

confluence-mcp-server

MCP server for fetching and parsing confluence.org point pages.

Tools

confluence_get_point

Fetches and parses a point directly from confluence.org.

Warning: confluence.org can be very slow (10+ seconds per page). The tool has a 30s timeout.

Parameters:

  • lat — signed integer latitude (e.g. 57, -33)

  • lon — signed integer longitude (e.g. 24, -3)

confluence_parse_html

Parses raw HTML you've already fetched yourself (e.g. via browser automation or curl). Useful for avoiding the slow server by batching fetches separately.

Parameters:

  • html — raw HTML string

  • lat — integer latitude

  • lon — integer longitude

Related MCP server: geolabel-mcp

Returned data

Both tools return a human-readable summary and a JSON object:

{
  lat: number;
  lon: number;
  prefix: string;            // "57°N 24°E"
  country: string;           // "Latvia"
  region?: string;           // "Euskadi" (not always present)
  locationDescription: string; // "4.8 km (3.0 miles) SW of Bolderāja, Rīgas, Latvia"
  distanceKm: number;        // 4.8
  direction: string;         // "SW"
  nearestPlace: string;      // "Bolderāja"
  altitudeM?: number;        // 19
  visitCount: number;        // 12
  notes?: string;            // contents of the Notes section, if present
}

The nearestPlace field is what you'll usually want to use as the entity name in the database — but confirm with Andrew since it's subjective (sometimes a better-known nearby town is preferable to the literally closest village).

Setup

npm install
npm run build

Claude Desktop config

{
  "mcpServers": {
    "confluence": {
      "command": "node",
      "args": ["/Users/andrewzc/Projects/confluence-mcp-server/dist/index.js"]
    }
  }
}

confluence-mcp-server

Available Tools

2 tools
confluence_get_pointA

Fetch and parse a confluence.org point page by latitude and longitude. Returns structured data about the point including country, nearest place, distance, visit count, and any notes. Warning: confluence.org can be slow (10+ seconds), so this tool has a 30s timeout.

ParametersJSON Schema
NameRequiredDescriptionDefault
latYesLatitude as a signed integer, e.g. 57 or -33
lonYesLongitude as a signed integer, e.g. 24 or -3

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral disclosure burden, and it does well by noting that confluence.org can be slow (10+ seconds) and that the tool has a 30s timeout. It also names the returned fields. This gives an agent useful operational expectations beyond the schema.

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?

Two short, front-loaded sentences convey the operation, return contents, and key performance warning without any filler. Every sentence earns its place.

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?

For a two-parameter tool with no output schema, the description covers the essential call context: what it does, what data it returns, and a critical timeout warning. It lacks only guidance on choosing between this tool and 'confluence_parse_html', but the core invocation context is sufficiently complete.

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 input schema already fully documents both parameters, including type, range, and examples, with 100% coverage. The description only restates 'latitude and longitude' and adds no additional parameter-specific meaning, so the baseline score applies.

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 uses a specific verb ('Fetch and parse') and a specific resource ('a confluence.org point page by latitude and longitude'), and it clearly states the structured data returned. This distinguishes the tool from the sibling 'confluence_parse_html' by emphasizing coordinate-based point lookup.

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 the tool is for fetching point data from lat/lon coordinates, which is useful context. However, it does not explicitly mention when to prefer this over the sibling 'confluence_parse_html' or state any exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

confluence_parse_htmlA

Parse raw HTML from a confluence.org point page. Useful when you've fetched the HTML yourself (e.g. via browser). Returns the same structured data as confluence_get_point.

ParametersJSON Schema
NameRequiredDescriptionDefault
latYesLatitude of the point (needed since it's not reliably in the HTML)
lonYesLongitude of the point
htmlYesRaw HTML content of the confluence.org page

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It communicates that the tool is a parser rather than a fetcher and that it returns the same data as confluence_get_point, but it does not mention behavior on invalid HTML, error handling, or coordinate validation. Reasonable but incomplete for a tool with no annotation safety profile.

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?

Two sentences with no filler. The core action is front-loaded, the usage condition follows immediately, and the output comparison to the sibling tool is packed into a short, skimmable clause.

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?

All three required parameters are fully documented, and the return type is anchored by referencing confluence_get_point's structured data. The description covers when to use it, what input to provide, and what to expect back. It is not exhaustive about errors or the exact output shape, but it is sufficient for an agent to invoke it correctly.

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 description coverage is 100%, with each parameter already meaningfully documented, especially the rationale for needing lat/lon. The description adds no additional parameter semantics beyond labeling html as raw HTML, so it meets the baseline but does not exceed it.

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 and resource: 'Parse raw HTML from a confluence.org point page.' The closing sentence ties it to the sibling tool's output, clearly distinguishing this parse operation from fetching via confluence_get_point.

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 a concrete use condition: 'Useful when you've fetched the HTML yourself (e.g. via browser).' It implies the alternative is confluence_get_point, but does not explicitly say 'use get_point when you have not fetched the HTML,' so exclusions are only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedconfluence_get_point
    • First observedconfluence_parse_html
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0
Disambiguation5/5

Both tools return the same structured data, but their inputs are clearly distinct (raw HTML vs lat/lon), and the descriptions explicitly state when to use each. There is no realistic selection ambiguity.

Naming Consistency5/5

Both tools use the same confluence_ prefix followed by a clear verb-noun pattern (get_point, parse_html). The naming is consistent and predictable.

Tool Count4/5

At two tools this is below the typical 3-15 range, but for the narrow read-only domain of fetching and parsing Confluence point pages, it is a reasonable minimal set without redundant tools.

Completeness5/5

The server covers the full implied workflow: either fetch a point by coordinates or parse already-fetched HTML into structured point data. There are no missing read operations or dead-end workflows for this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

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/azamlerc/confluence-mcp-server'

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