MCP server
Splitkick has a built-in Model Context Protocol server. An agent connected to it can see what you see in the app and act on it: list projects and sessions, create a worktree, start a session, read another session's messages, commit, push, open a pull request.
Set-up
The server is always available to the agents; Splitkick repairs the configuration on start. You can also use third-party MCP servers in your sessions: Settings → MCP Servers, with overrides per project.
What agents can do
| Area | Tools (selection) |
|---|---|
| Orientation | get_current_context, list_projects, list_all_sessions, search_sessions |
| Worktrees | create_worktree, create_worktree_from_existing_branch, archive_worktree, get_worktree_diff |
| Sessions | create_session, send_chat_message, read_session_messages, set_session_model, set_session_status |
| Ship | create_commit, push_worktree, create_pull_request, merge_pull_request, run_review |
| Forges | list_github_issues, list_github_prs, list_security_issues, list_linear_issues |
| Other | get_usage, open_in_browser, start_run_environment |
Agents can mark their own session as done with set_session_status, so a long-running task can tidy up after itself.
Agent browser
A second MCP server, Agent Browser, gives agents a browser with a profile you log in to once. Install it from Settings → MCP Servers → Agent Browser; it needs npm on your PATH.