What can the Compliance Glossary MCP server access?

Only public pages published on the Compliance Glossary for Confluence website. It cannot access customer Confluence spaces, Forge tenant data, or private evidence.

Can the MCP server change Confluence data?

No. The server exposes only read-only search and fetch tools and has no connection to customer Confluence or Forge APIs.

Public MCP Server — Compliance Glossary for Confluence

Connect to the server

Add this remote MCP URL in an MCP-compatible client:

https://assistant.compliance-glossary.teamkit.dev/mcp

Open the client’s connector or MCP settings.
Add a remote server using the URL above. No credentials are required.
Confirm that the client discovers the search and fetch tools.

Client availability and setup labels depend on the AI product and account plan.

Available tools

`search`

Finds up to five relevant passages from published Compliance Glossary pages and returns their canonical URLs.

`fetch`

Returns one exact published page selected by its canonical URL, including its description, verification date, and content hash.

Data boundary

The server reads a generated index of the public website. It has no customer authentication, Atlassian scopes, Forge API connection, model credentials, or write tools.

No access to customer Confluence spaces or tenant data.
No access to private evidence baselines.
No term creation, approval, scan, export, or other write action.
No legal conclusions, compliance certification, or guarantee.

Important: the MCP server provides public source material. The connected AI client composes its own answer and applies its own data-handling terms.

Service behavior

Transport: stateless MCP over Streamable HTTP.
Sources: canonical, indexable pages on this website only.
Access: anonymous, read-only, and rate-limited.
Health: assistant.compliance-glossary.teamkit.dev/health.

Compliance Glossary MCP Server