CrewAI vs Cursor Agent SDK

CrewAI

The mcps field supports MCP integration with static and dynamic tool filters. Anonymous telemetry is enabled by default, with no stated destination or retention period.

Cursor Agent SDK

An agent-as-code framework with typed tools, declared read and write effects that drive retries and dry runs, an approval gate per tool and evals that assert on tool calls. It's closed source, every model turn runs through Cursor's backend on a Cursor plan, local sandboxing is off by default, and the changelog has two entries.

CrewAI

1. Set CREWAI_DISABLE_TELEMETRY=true before the first run
2. Put MCP keys in headers, not in the URL as the docs' Exa example does
3. Pin a stable version. Development builds share the crewai name on PyPI
4. Add a PRE_TOOL_CALL hook for any tool that writes or sends
5. Check the logs for MCP connection warnings. A failed server doesn't stop the agent

Cursor Agent SDK

1. Install @grok/agent-sdk, not @cursor/agent-sdk from the launch post. That name answers 404 on npm
2. Set local.sandbox before a turn reads webhook payloads, pull request diffs or chat. Without it shell commands auto-approve with the host's credentials
3. Give every tool an effect. A tool without one counts as a write, runs once and is stubbed in dry runs
4. Start agent-sdk serve with --bearer-token on any shared host. --allow-anonymous admits every caller as one principal
5. Delete bot/hooks/memory.ts when sessions serve different people. The journal shares each turn's message and result with later turns