# Nimbled

> Nimbled is an agent orchestration platform: build agents, give them guard-railed tools, chain them into workflows, and run them behind one API — or let an agent drive Nimbled directly over MCP. One execution engine, three surfaces: the app UI, a REST API, and an MCP server.

Full version: https://nimbled.dev/llms-full.txt

## For agents (MCP)

Nimbled runs a stateless Model Context Protocol server (revision 2026-07-28, with a compatibility shim for older hosts) so any agent host — Claude, Cursor, or your own agent — can build and run Nimbled workflows natively.

- Endpoint: https://api.nimbled.dev/mcp
- Auth: `Authorization: Bearer <nimbled_api_key>` (keys look like `nk_live_…`; create one in the Developer portal). Every call is scoped to the key's owner.
- Tools: `nimbled_guide`, `list_workflows`, `list_agents`, `list_connectors`, `run_workflow`, `invoke_agent`, `get_run`
- Typical flow: `list_workflows` → `run_workflow { workflow, input }` → `get_run { run_id }`
- Guide: https://docs.nimbled.dev/mcp

## Docs

- Introduction: https://docs.nimbled.dev/introduction
- Quickstart: https://docs.nimbled.dev/quickstart
- Authentication: https://docs.nimbled.dev/authentication
- MCP server: https://docs.nimbled.dev/mcp
- Webhooks & scheduled triggers: https://docs.nimbled.dev/webhooks
- API reference: https://docs.nimbled.dev/api

## REST API

- Base URL: https://api.nimbled.dev/v1 (`Authorization: Bearer nk_live_…`)
- Resources: keys, agents, workflows, runs, connectors, webhooks
- Runs are synchronous — the response is the finished run, with per-step logs including tool calls.

## Connectors

Slack, GitHub, Jira, Notion, OpenRouter, Monid, Zapier (more on the roadmap). Connect once, grant per agent.