Expand your GitBook Docs MCP with MCP Studio by Appa Tools

Combine current guidance with code examples

A public GitBook site can expose its documentation through an MCP endpoint. Public GitHub repositories can provide sample applications, configuration files, tests, and implementation details. MCP Studio can put both source types behind one MCP server.

This source set is useful when a question needs both the supported workflow and a concrete implementation. For example:

How do I initialize the client in Vue and handle a paginated response?

GitBook can return the current initialization and pagination guidance. A Vue sample repository can return imports, component structure, and working request code. The client connects to one MCP Studio endpoint and can retrieve from both.

Federation and indexing use different paths

MCP Studio treats the GitBook MCP endpoint as a federated source. It does not copy the GitBook site into its own index for this connection. When a request arrives, MCP Studio:

1. Inspects the remote server's tools/list schema.
2. Selects a retrieval tool that matches the requested MCP Studio tool.
3. Builds arguments from the remote tool's input schema.
4. Calls the remote GitBook server.
5. Combines the returned text with results from indexed sources.

This is live federation. Published GitBook updates are available through the remote endpoint without waiting for MCP Studio to recrawl the site.

GitHub repositories follow the indexing path. MCP Studio crawls repository content, splits it into passages, creates embeddings, and stores searchable records. Repository files can then participate in semantic and full text retrieval.

The tradeoff is explicit:

Source	Retrieval model	Update behavior
Public GitBook MCP	Live federation	Reads current results from GitBook at request time
Public GitHub repository	MCP Studio index	Updates after initial indexing and later refreshes

Federation depends on the remote server's availability, latency, tool schemas, and returned content. Indexing depends on crawl completion and refresh timing.

Configure the GitBook endpoint

You need a published GitBook site with Page actions enabled under Site customization.

Append /~gitbook/mcp to the published site URL. If the documentation is at:

https://acme.com/docs

the public MCP endpoint is:

https://acme.com/docs/~gitbook/mcp

GitBook returns a 404 for this endpoint when Page actions is disabled. Confirm the endpoint is reachable before adding it to MCP Studio.

This guide applies to public GitBook sites. Login gated GitBook sites use /~gitbook/mcp/auth with OAuth, which MCP Studio does not currently support.

Build the combined server

The free tier includes two sources, enough for one public GitBook endpoint and one public GitHub repository.

1. Open the MCP Studio wizard.
2. Create a server with a product scoped name such as acme-context.
3. Add https://acme.com/docs/~gitbook/mcp as the first source.
4. When asked about authentication, choose No, it's public.
5. Let MCP Studio inspect the remote tools. The source check reports whether any tools can be queried with the supported retrieval flow.
6. Add a public GitHub repository URL as the second source.
7. Enable search_docs, ask_question, and get_code_examples. Add find_api_reference when the documentation includes API reference content.
8. Deploy the server and wait for the repository index to complete.

Add the generated endpoint to the MCP client:

{
  "mcpServers": {
    "acme-context": {
      "url": "https://appatools.com/mcp-studio/api/mcp/acme-context-h8w2v5"
    }
  }
}

The client needs only the MCP Studio entry. It does not need separate GitBook and GitHub connections for this source set.

Test each retrieval path

Use questions with expected answers before sharing the server.

First test GitBook federation:

• What is the recommended authentication flow?
• Which parameters are required for pagination?
• What does the current documentation say about error handling?

Then test repository indexing:

• Show the Vue initialization example.
• Which configuration values does the React sample load?
• Find code that handles paginated responses.

Finally test combined retrieval:

• Explain the recommended pagination workflow and show where the Vue sample implements it.
• Compare the documented authentication flow with the configuration used in the React example.

Inspect the cited sources. A combined answer should distinguish published guidance from repository implementation. If one source consistently dominates, make the question more explicit, choose a more focused repository, or use the tool whose retrieval intent matches the task.

Add repositories only when they have a defined role. Clear source roles make testing and analytics easier to interpret.

Understand remote tool selection

MCP Studio does not call arbitrary tools on a federated server. It prefers known retrieval tool names, then considers other tools with retrieval signals. Published annotations such as readOnlyHint and destructiveHint are used when available. Tool names that indicate mutation are excluded, and a tool without a retrieval signal is not used as a fallback.

Required arguments must be constructible from the remote tool's schema. If a tool requires a value MCP Studio cannot infer, that tool is skipped. A successful tools/list response therefore does not guarantee that the source has a queryable tool. The source check reports queryable tools separately.

Another MCP endpoint may require domain specific identifiers that cannot be derived from a general question.

Use analytics to evaluate the source set

MCP Studio records telemetry for requests that use indexed and federated sources.

Free analytics include request counts, calls over time, and breakdowns by tool and source. These views can show whether developers use get_code_examples, whether GitBook participates in responses, and whether a repository contributes to the questions it was added to.

The Action tier adds per-request details, associated passages, retrieval confidence, answerability, and content gaps. New accounts receive a 30 day trial with all analytics tiers. Telemetry is recorded on every request; the active tier controls which views are returned.

Use the data to make source decisions:

• A repository that never contributes may be too broad, poorly indexed, or unrelated to actual questions.
• Repeated code example requests may justify adding another focused sample repository.
• Questions with low confidence may identify missing guidance or examples.
• Strong GitBook participation with weak repository participation may indicate that the combined test questions are too documentation focused.

Analytics do not prove that an answer or code sample is correct. Keep known questions and verify cited passages after source changes.

Current limitations

Federation is retrieval only. MCP Studio does not expose remote action tools that send messages, modify data, create pull requests, or perform other writes.

Federated output is bounded. Each federated source contributes up to about 6,000 characters per request. Focused questions reduce the chance that relevant content is displaced.

Remote calls have a time budget. A federated source receives about 12 seconds. MCP Studio reserves time for fallback retrieval when the first selected tool is slow.

Remote availability affects answers. A GitBook outage, timeout, schema change, or tool error can prevent that source from contributing. Indexed GitHub results can still be returned.

OAuth protected GitBook endpoints are unsupported. /~gitbook/mcp/auth cannot currently complete its OAuth flow through MCP Studio.

Private repositories change server access. Adding a private GitHub repository forces the MCP Studio server to private visibility. Clients then need a server scoped mcps_live_ access token.

Indexed repositories are not live. Changes appear after a refresh, not immediately after a Git push.

For source configuration details, see MCP server sources, adding sources, and the dashboard guide.