Connect Samva to Executor
Add Samva's hosted MCP server or OpenAPI description to Executor and authenticate it safely.
Executor indexes MCP servers and OpenAPI descriptions into a governed tool catalog. Add Samva once, set authentication and approval policies, then expose the selected email tools to the agents connected to your Executor workspace.
Choose a surface
Samva publishes two surfaces that Executor can import. Choose one based on the work your agents need to perform.
| Surface | Import URL | Choose it when |
|---|---|---|
| Hosted MCP | https://mcp.samva.dev | You want curated, organization-scoped agent tools and automatic OAuth discovery. |
| REST API | https://api.samva.dev/v1/openapi.json | You need broader API coverage or direct OpenAPI operations. |
The samva CLI is a separate terminal surface. Do not add it as an Executor integration.
Executor consumes the integrations.sh catalog. You can inspect Samva's published catalog entry at integrations.sh/samva.dev. Samva's owner declaration and live endpoints remain the underlying authority.
Add hosted MCP
- Open Integrations in Executor and select Add Integration.
- Search for Samva, or paste
https://mcp.samva.dev. - Select the hosted MCP surface.
- Choose an authentication method:
- Use OAuth for an interactive connection. Executor follows Samva's protected-resource metadata and opens the browser consent flow.
- Use an organization API key and send it in the
X-API-Keyheader for unattended automation.
- Review the discovered tool schemas before saving the integration.
See Connect an agent over MCP for Samva's authentication and tool contract.
Add the REST API
- Open Integrations in Executor and select Add Integration.
- Paste
https://api.samva.dev/v1/openapi.json. - If Executor asks for a base URL, enter
https://api.samva.dev/v1. - Add an API-key authentication method with header name
X-API-Key. - Review the imported operations and enable only the ones the connected agents need.
Create and scope the key as described in API keys.
Set safe policies
Start with read operations and inspect the resulting tool names and schemas. Before enabling a send:
- Verify the organization and sending domain associated with the credential.
- Require approval for message sends and other consequential writes.
- Use a stable idempotency key for any send an automation may retry.
- Run a deliberate test only when a real delivery is intended.
Executor owns its tool policies. Samva still enforces the credential's organization and API-key permissions on every request.