# Tools & integrations for AI agents

How the agent acts inside other people's software, and who holds the token when it does.

6 options tracked · 5 open source · 4 self-hostable · optional

## All options

| Option | What it does | Licence | Self-host | Page |
| --- | --- | --- | --- | --- |
| MCP (Model Context Protocol) | The open protocol for exposing tools and data to agents. The default answer. | open source | yes | https://newagent.build/c/mcp |
| Composio | Managed auth and tool-calling for 250+ SaaS apps. | open source | no | https://newagent.build/c/composio |
| Arcade | Tool-calling with per-user OAuth, so the agent acts as the user, not as root. | open source | yes | https://newagent.build/c/arcade |
| Browserbase | Managed headless browsers with stealth and session replay, plus Stagehand. | proprietary | no | https://newagent.build/c/browserbase |
| Playwright MCP | Drive a real local browser over MCP, using the accessibility tree. | open source | yes | https://newagent.build/c/playwright-mcp |
| Nango | Open-source integration platform — you own the OAuth and the sync logic. | open source | yes | https://newagent.build/c/nango |

## Machine interfaces

- `GET https://newagent.build/api/registry` — every component as JSON
- `GET https://newagent.build/api/vendors` — vendors, with the repo and releases feed to watch
- `GET https://newagent.build/api/advise?q=<plain english>` — recommended stack for a description
- `GET https://newagent.build/api/stack?<layer>=<id>&format=sh|json|md|yml|agents|env` — a stack as files
- `GET https://newagent.build/llms.txt` — the whole registry in one fetch

Any page here also returns markdown if you send `Accept: text/markdown`.