forkast-mcp-docs
Server Details
MCP server for querying Forkast documentation
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.3/5 across 4 of 4 tools scored.
Each tool has a clearly distinct purpose: get_all_docs retrieves all documents, get_doc fetches a single document by ID, search_query performs full-text content search, and search_title searches by title only. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case: get_all_docs, get_doc, search_query, and search_title. The naming is predictable and readable, using clear verbs (get, search) paired with descriptive nouns that indicate the tool's specific function.
With 4 tools, the server is well-scoped for its purpose of accessing Forkast documentation. Each tool earns its place by covering distinct aspects: bulk retrieval, single document access, and two types of search. This count is neither too thin nor excessive for the domain.
The toolset provides strong coverage for reading and searching documentation, including all-docs, single-doc, and search functionalities. A minor gap exists in the lack of write operations (e.g., create, update, delete documents), but for a documentation access server, the surface is largely complete and supports core agent workflows without dead ends.
Available Tools
4 toolsget_all_docsInspect
Retrieve every document in the Forkast documentation space
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_docInspect
Retrieve a single document by its Archbee document ID
| Name | Required | Description | Default |
|---|---|---|---|
| docId | Yes | The Archbee document ID |
search_queryInspect
Full-text search across Forkast documentation content
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query text |
search_titleInspect
Search Forkast documentation by document title
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Title search text |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!