Where does the configuration go?
llama-index-tools-mcp: BasicMCPClient and McpToolSpec.
pip install llama-index-tools-mcp How do I connect LlamaIndex?
- pip install llama-index-tools-mcp.
- Create BasicMCPClient and McpToolSpec as below.
- Hand the tools to a FunctionAgent or another LlamaIndex agent.
import os
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
http_client = BasicMCPClient(
"https://api.nofeb.com/mcp",
headers={"Authorization": f"Bearer {os.environ['NOFEB_API_KEY']}"},
)
mcp_tool_spec = McpToolSpec(client=http_client)
tools = await mcp_tool_spec.to_tool_list_async() Checked against LlamaIndex's documentation on . source: github.com
What should I know about LlamaIndex's setup?
- Streamable HTTP is used unless the URL path ends in /sse or asks for SSE.
- Passing your own http_client makes BasicMCPClient ignore headers.
What can I ask it to do?
An agent that reads invoice emails from the AP inbox, using attachment text from get_message, and records invoice numbers with set_message_metadata.
117 tools are available, including create_inbox, wait_for_email, reply_to_message, get_thread_context, set_thread_state and get_dns_setup. Whether a send goes out at once or waits for a person is decided by the inbox's autonomy tier on the server, not by LlamaIndex.
Frequently asked questions
Why are my headers ignored?
If you pass your own http_client to BasicMCPClient, it ignores headers; set the header on that client instead.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| MCP server | A remote MCP server over streamable HTTP whose tools are generated from the same operation table as the REST API and dispatched through the same router, so a tool cannot behave differently from its endpoint. | Shipped |
| Scoped API keys | Keys bound to the organization, one pod or one inbox, holding only the scopes they are given. A key cannot mint a key wider than itself. | Shipped |
| Autonomy tiers enforced by the server | Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. | Shipped |
| Wait for an email | Long-poll an inbox for up to a minute until a message matching sender, subject or has-a-code arrives. | Shipped |
| TypeScript and Python SDKs | Official clients generated from the OpenAPI document: @nofeb/sdk for Node, Deno, Bun and edge runtimes, and nofeb for Python with sync and asyncio clients. Both chain long polls for waitForEmail, retry idempotent requests, page through lists and verify webhook signatures. | Shipped |
| MCP sign-in with OAuth | MCP clients connect by signing in instead of pasting a key: OAuth 2.1 with discovery, dynamic client registration, client ID metadata documents, PKCE, tokens bound to the MCP server, refresh-token rotation and immediate revocation. A person approves the scopes, and optionally one inbox, in the console, and can disconnect the app at any time. API keys keep working beside it. | Shipped |