chore: add tessl multi-agent MCP configuration - #192
Merged
Conversation
Add tessl CLI MCP server configuration generated by `tessl init` so contributors get the `tessl` MCP server (tessl mcp start) wired into every supported agent runtime. - .mcp.json: fix invalid mcpServers: [] (array) → object; add tessl server (Claude Code) - .gemini/settings.json: add tessl server (Gemini CLI) - .cursor/mcp.json: Cursor MCP config - .codex/config.toml: Codex MCP config - .vscode/mcp.json: VS Code / GitHub Copilot MCP config - tessl.json: tessl project manifest
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Code Review
This pull request adds configuration files for the tessl MCP server across multiple editors and environments, including Codex, Cursor, VS Code, and a general MCP configuration, along with a tessl.json project file. The reviewer pointed out that .gemini/settings.json, which was mentioned in the PR description, is missing from the changes and should be added.
Contributor
There was a problem hiding this comment.
No issues found across 6 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Architecture diagram
sequenceDiagram
participant CC as Claude Code
participant GC as Gemini CLI
participant Cur as Cursor
participant Cdx as Codex
participant VSC as VS Code/Copilot
participant MCP as tessl MCP Server
participant Tessl as tessl CLI
participant Manifest as tessl.json
Note over CC,VSC: NEW: Multi-agent MCP configuration
CC->>MCP: Read .mcp.json - mcpServers.tessl
GC->>MCP: Read .gemini/settings.json - mcpServers.tessl
Cur->>MCP: Read .cursor/mcp.json - mcpServers.tessl
Cdx->>MCP: Read .codex/config.toml - mcp_servers.tessl
VSC->>MCP: Read .vscode/mcp.json - mcpServers.tessl
MCP->>Tessl: Execute "tessl mcp start" (stdio)
Tessl->>Manifest: Read tessl.json for project config
Manifest-->>Tessl: Project name, mode, dependencies
Tessl-->>MCP: MCP protocol responses (tools, resources, etc.)
MCP-->>CC: MCP tools available
MCP-->>GC: MCP tools available
MCP-->>Cur: MCP tools available
MCP-->>Cdx: MCP tools available
MCP-->>VSC: MCP tools available
Note over CC,VSC: All agents now have tessl MCP integration
The use-bun description was ~1900 chars, exceeding Claude Code's default maxSkillDescriptionChars (1536), so trailing triggers were silently truncated and never loaded at skill-selection time. Consolidate the redundant enumerated (1)-(7) list and "Triggers on:" list into one de-duplicated ~843-char sentence, preserving the high-signal triggers.
…file CI apps/web and packages/vitest-config declared "@nuxt/devtools": "latest" and "typescript": "latest". The "latest" dist-tag re-resolves on every install, so the committed bun.lock could never satisfy CI's `bun install --frozen-lockfile` — it failed perpetually as upstream published new releases. - apps/web: @nuxt/devtools "latest" -> 4.0.0-alpha.6 - packages/vitest-config: typescript "latest" -> ^6.0.2 - regenerate bun.lock with the pinned bun@1.3.10; this also syncs the gatekeeper workspace version (1.3.0 -> 1.4.0) that a prior release bumped in package.json without regenerating the lockfile. Verified: bun install --frozen-lockfile now passes deterministically.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
tesslCLI multi-agent MCP configuration generated bytessl init, so contributors get thetesslMCP server (tessl mcp start) wired into every supported agent.Changes
.mcp.json— fix invalidmcpServers: []→ object; addtesslserver (Claude Code).gemini/settings.json— addtesslserver (Gemini CLI).cursor/mcp.json— Cursor MCP config.codex/config.toml— Codex MCP config.vscode/mcp.json— VS Code / GitHub Copilot MCP configtessl.json— tessl project manifestNotes
The previous
.mcp.jsonhad"mcpServers": [](an array), which is schema-invalid for Claude Code and blockedtessl init. Corrected to an object.Summary by cubic
Adds multi‑agent MCP config for
tessl, wiring thetesslserver (tessl mcp start) into Claude Code, Gemini CLI, Cursor, Codex, and VS Code/Copilot. Also pins@nuxt/devtoolsandtypescriptand regeneratesbun.lockto fix frozen‑lockfile CI installs.New Features
tesslMCP config for Claude Code, Gemini CLI, Cursor, Codex, and VS Code/Copilot, plustessl.jsonmanifest.Bug Fixes
.mcp.jsonby changingmcpServersfrom an array to an object and shortens theuse-bunskill description under the 1536‑char Claude Code cap so triggers load.@nuxt/devtoolsandtypescriptversions and regeneratesbun.locksobun install --frozen-lockfileis deterministic.Written for commit dca53fd. Summary will update on new commits.