How do AI agents use Motion through Open Connector?

Your user connects Motion once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Motion tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Motion MCP server?

Yes. Open Connector can serve Motion as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Motion actions with credentials injected server-side.

Where do Motion credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Motion integration

Motion integration for AI agents.

Motion integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Motion tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Motion actions, managed and audited.

Your user connects Motion once; your agent can then motion is the #1 Rated Productivity Platform for the AI Era. AI Projects, AI Tasks, AI Calendar, AI Meetings, AI Docs, AI Notes, AI Reports, AI Workflows, and more — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Motion access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Motion tools.

0 tools are generated from the published Motion catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.

No tools match “”.

FAQ

Motion integration, answered

How do AI agents use Motion through Open Connector?: Your user connects Motion once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Motion tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Motion MCP server?: Yes. Open Connector can serve Motion as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Motion actions with credentials injected server-side.
Where do Motion credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Motion — keep the keys.

Open source, self-hostable, with Motion credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →