Docs
Add notanATS to Composio (Custom MCP)
notanATS is not in Composio's public catalogue, but you can add it to your own Composio project as a Custom MCP server. Your agents then get all 12 notanATS tools — positions, applicants, calibration progress, and candidate decisions — inside your Composio sessions. (Candidate decisions made through an agent are proposals: a hiring manager approves them in notanATS before anything changes.)
Custom MCP is a Composio feature labelled experimental, so its APIs may change.
Before you start
- A Composio project (shared toolkits work on every plan; a toolkit private to one user needs a Pro plan).
- A notanATS account where you can create API keys.
Step 1 — Create a notanATS API key
- Sign in to notanATS and open Settings → API Keys.
- Create a new key and turn on agent access for it.
- Copy the key. It starts with
nagt_. Treat it like a password — anyone with it can act through your notanATS account within the key's permissions.
Step 2 — Create the Custom MCP toolkit in Composio
Use the Composio SDK (composio.experimental.custom_toolkits in Python, composio.experimental.customToolkits in TypeScript) or the Custom MCP API to create a toolkit with:
| Field | Value |
|---|---|
| Name | notanATS |
mcp_url | https://notanats.com/mcp (use this exact final URL — no redirects, and never put your key in the URL) |
auth_schemes | |
user_id | "all" to share the toolkit with every user in your project, or your own user ID to keep it private (Pro plan) |
Save the CUSTOM_* slug Composio returns — you need it to use, sync, or delete the toolkit. The URL and auth settings cannot be changed later; to change them, delete the toolkit and create it again.
Step 3 — Connect your notanATS key
If the create call returns a connect_link, open its redirect_url and enter your nagt_ key when asked. Your tools sync automatically when the first account connects — all 12 notanATS tools should appear on the toolkit.
Step 4 — Use it in a session
Add the toolkit's CUSTOM_* slug to your session's tools. Your agent finds the notanATS tools through Composio's tool search and uses your connected key automatically.
About OAuth — read this before you try it
Composio's Custom MCP supports OAuth only through Dynamic Client Registration (DCR). notanATS does not offer DCR; it signs agents in with Client ID Metadata Documents (CIMD), which Composio's docs state are not supported. So the OAuth option will not connect today — use the API-key steps above. If notanATS adds DCR support, this guide will be updated.
Notes and limits
- Revoking access: deleting the toolkit in Composio does not revoke your key on the notanATS side. To cut access completely, also revoke the key in notanATS under Settings → API Keys.
- Tool changes: Composio does not resync automatically. If notanATS adds or changes tools, run a sync on the toolkit.
- One toolkit per URL: creating the same server URL twice for the same scope returns an error — update the existing toolkit instead of creating a second one.