The SSE protocol will be deprecated soon. Please use streamable-http as the connectionType moving forward.

​
Prerequisites

To get the most out of this guide, you’ll need to:

​
1. Create a Motion MCP Server

Use the following endpoint to create a new remote Motion MCP server instance:

​
Request

curl --request POST \
  --url https://api.klavis.ai/mcp-server/instance/create \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
  "serverName": "Motion",
  "userId": "<YOUR_USER_ID>",
  "platformName": "<YOUR_PLATFORM_NAME>"
}'

​
Response

{
  "serverUrl": "https://motion-mcp-server.klavis.ai/sse?instance_id=<instance-id>",
  "instanceId": "<instance-id>"
}
serverUrl specifies the endpoint of the Motion MCP server, which allows you to manage tasks, projects, and workspaces through the Motion service.
instanceId is used for authentication and identification of your server instance.

​
2. Configure Motion API Key

To use the Motion MCP Server, you need to configure it with your Motion API key.

​
Setting up Motion API Key

curl --request POST \
  --url https://api.klavis.ai/mcp-server/instance/set-auth-token \
  --header 'Authorization: Bearer <YOUR_KLAVIS_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
  "instanceId": "<YOUR_INSTANCE_ID>",
  "authToken": "<YOUR_MOTION_API_KEY>"
}'

​
Response

{
  "success": true,
  "message": "<string>"
}

​
Explore MCP Server Tools