MCP Tools#
The Model Context Protocol is how an agent reaches systems outside its own shell: mail, issue trackers, databases, your internal APIs. LIT does not implement MCP itself. The harness does (Claude Code, Codex CLI, Gemini CLI). LIT decides which servers each agent gets, with which credentials, under whose rules.
What's connected#
Google Workspace. Gmail, Drive and Calendar, connected by one OAuth button in the Google Workspace app and wired to the agent automatically. The token belongs to the user who clicked Connect and lives in their own storage. See Skills, Apps & Integrations.
Jira. Search with JQL, create and update issues, comment, transition, assign, link — configured once with the team's Jira URL and a per-user API token.
Agent messaging and heartbeat controls. Two servers ship with the platform: one lets agents send messages to each other and to their user; the other lets an autonomous agent adjust its own sleep interval, wake, pause or resume. See Heartbeat.
Anything else. Any MCP server that speaks stdio works: the reference servers (filesystem, git, databases, browsers) or one you write in Python or TypeScript for your own systems.
Configuration, three tiers#
Server definitions resolve from global to agent to channel, each tier overriding the one below:
- Global — servers every agent on the host may use, in the host config.
- Agent — in the agent's settings: a checklist of available servers and, where needed, overrides (a different working directory for the filesystem server, a project key for Jira).
- Channel — a channel can narrow the list further for work that happens there.
An agent only sees the servers it was given. Two agents on the same host can have entirely different toolsets — a project manager with Jira and messaging, a developer with git and the filesystem — and neither can reach the other's.
Runs as the user#
Every MCP server spawns inside the user's own harness session, over SSH, as that user's Linux account. A Jira token is that person's token. The filesystem server can see what that person can see. There is no service account with everyone's credentials, and the record shows which identity made every call. See Identity & Security.
Governed by policy#
A team can say which MCP servers its members may connect at all, team-wide and per group, with allow and deny lists in the same grammar as model and seat rules. Deny wins. A member who is not allowed a server cannot connect it, and the refusal is a reply they can read rather than a silent failure. The same rule is pushed into the harness's managed settings, so it holds for a claude a member launches from a shell. Details in Seats & Policy.
Adding a custom server#
Write the server (the MCP SDKs for Python and TypeScript are a few dozen lines for a first tool), register it in the host config or in an agent's overrides with its command, arguments and environment, and tick it on for the agents that need it. The tool appears in the agent's next session.
The limitation this removes: the agent could only touch what was on its own disk. With MCP it can touch what you can touch, and nothing you cannot.