Skip to content
nofeb

nofeb with CrewAI

Agent framework · configuration checked against the vendor's documentation on 2026-10-01

Give a CrewAI Agent an mcps list containing MCPServerHTTP with the nofeb URL, an Authorization header and streamable=True. The agent gets nofeb's tools for its tasks, with the tool list cached between runs.

Checked against the engine on .

Where does the configuration go?

The Agent mcps field with crewai.mcp.MCPServerHTTP.

Install
pip install crewai   # depends on mcp; for MCPServerAdapter: pip install 'crewai-tools[mcp]'

How do I connect CrewAI?

  1. pip install crewai.
  2. Add MCPServerHTTP from crewai.mcp to the agent's mcps field as below.
  3. Give the agent a task that needs email, such as collecting a vendor's reply.
CrewAI: Python
import os
from crewai import Agent
from crewai.mcp import MCPServerHTTP

agent = Agent(
    role="Mail operator",
    goal="Handle email for the user",
    backstory="Uses nofeb inboxes.",
    mcps=[
        MCPServerHTTP(
            url="https://api.nofeb.com/mcp",
            headers={"Authorization": f"Bearer {os.environ['NOFEB_API_KEY']}"},
            streamable=True,
            cache_tools_list=True,
        )
    ],
)

Checked against CrewAI's documentation on . source: docs.crewai.com

What should I know about CrewAI's setup?

  • Field names checked against crewai 1.15's crewai.mcp configuration.

What can I ask it to do?

A "Mail operator" agent that waits for the supplier's reply in the quotes inbox and records the quoted price on the thread with set_thread_state.

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 CrewAI.

Frequently asked questions

Should I use MCPServerAdapter instead?

MCPServerHTTP takes headers explicitly; the older MCPServerAdapter docs do not show a headers key, so prefer MCPServerHTTP for an authenticated server.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
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