SearchAPI MCP for AI agents
Agents read SearchAPI MCP at once. Changes and sends are held for a person's approval by default.
About SearchAPI MCP
SearchAPI MCP lets agents call configured search engines through a hosted OAuth integration with plan and request quotas.
What an agent can do in SearchAPI MCP
Every SearchAPI MCP action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in SearchAPI MCP without asking first. 1 action.
- Google search lightPerform fast Google web searches. Returns organic search results, related searches, and pagination. Suitable for quick information retrieval when advanced filtering is not needed. Requires a search qu
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 0 actions.
None in this connector.
SearchAPI MCP questions
Can an agent change data in SearchAPI MCP on its own?
Not by default. Changes and sends in SearchAPI MCP are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in SearchAPI MCP?
This connector lists 1 read action. Reads run at once, without waiting for approval.
How does SearchAPI MCP connect?
It connects with dcr oauth. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.