Choose where it can work
Connect with interactive MCP authorization or issue a key limited to the project, capabilities, and sender domains the job needs.
Project + capability + domain grantLet your coding agent finish the email integration.
Connect NoticeAPI over MCP or issue a scoped project key. Your agent can discover the API, write the send path, and inspect the result without reaching billing, members, or another project.
Agent implementationBounded
Task
Add a receipt email to the checkout application.
- Project
- checkout-app
- Domain
- mail.example.com
- Capabilities
- email:send · templates:write
- Discovery
- Hosted MCP · OpenAPI 3.1
Outside the grantBilling · members · other projects
Ready to implement inside checkout-app
Agent transportHosted + local MCP
Machine contractOpenAPI 3.1
Grant boundaryCapability · project · domain
Runtime optionsREST · Node · SMTP
From task to working code
Three parts your team can see.
The human chooses the boundary and reviews the implementation. The agent gets a real contract instead of guessing endpoints.
Let it read the real contract
MCP exposes structured tools. OpenAPI 3.1 describes the same REST resources, inputs, responses, and stable error codes.
Hosted MCP + OpenAPI 3.1Review code and outcome
The agent implements the application path, uses a verified sender, and reads the recipient timeline or signed webhook after the request.
Code in your app + delivery recordDiscovery surfaces
Use the interface your agent host supports.
MCP and OpenAPI describe the platform. REST, Node, or SMTP can run the code your application keeps.
Hosted MCP
https://mcp.noticeapi.com/mcpStreamable HTTP with interactive OAuth or an explicit bearer key. Choose capabilities and project access during authorization.Connect hosted MCPLocal MCPnoticeapi mcpRun the stdio server inside the agent host and keep the scoped API key in the local process environment.Read local setupOpenAPI 3.1/openapi.jsonGenerate or inspect direct REST requests from the canonical machine-readable contract used by the platform.Open the schemaNode SDK and CLInpm install noticeapiUse typed application calls, project selection, and direct commands when MCP is not the right runtime interface.Read SDK setupWhat it can implement
The email work around the application.
Keep the agent inside one project while it builds the workflow the product actually needs.
Transactional emailAdd receipts, resets, verification, and alerts with retry-safe sends.Marketing emailCreate opted-in audiences, broadcasts, schedules, and recipient results.Lifecycle automationsConnect audience triggers to stored template steps, delays, and stops.Inbound emailRoute parsed messages and attachments into application code on Pro.
Before you connect it
Clear boundaries for humans and agents.
Does a coding agent need full workspace access?
No. Use sending-only access for a runtime integration or a custom grant limited to selected capabilities, projects, and domains. Full access is available for a trusted personal agent, but it is not the default requirement.
Can an agent create another API key?
Only when its own grant includes api-keys:write. Any credential it creates must be equal to or narrower than the credential making the request.
Can MCP bypass suppressions or plan limits?
No. The grant decides which operation may be attempted. Project boundaries, domain rules, suppressions, unsubscribe state, quotas, pauses, and acceptable-use controls are still enforced afterward.
Do we have to use MCP in production?
No. MCP can help the coding agent discover and implement the integration. Your application can run the finished workflow through REST, the Node SDK, or SMTP.
First implementation
Connect one project. Give the agent one real email job.
Start free with a scoped key, or connect a compatible client to the hosted MCP server.