feat(evi): allow the agent to create and manage linear initiatives - #554
Merged
Conversation
Linear's hosted MCP exposes save_initiative (create or edit an initiative) and save_initiative_update (post an initiative status update); both were left off the connection allowlist, so initiatives stayed read-only for the agent. Add them to ALLOWED_TOOLS and update the connection description. Deletes and structural writes for projects and releases remain excluded. Checks: typecheck, lint, and evi tests all pass.
|
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
commit: |
Linear's hosted MCP exposes save_initiative (create or edit an initiative); it was left off the connection allowlist, so initiatives stayed read-only for the agent. Add it to ALLOWED_TOOLS and update the connection description. Initiative status updates stay excluded: the tool name is unverified against the live server, and a runtime probe of mcp.linear.app found no analogous project-update tool. Re-enable only after a live tools/list confirms the name. Deletes and structural writes for projects and releases remain excluded. Checks: typecheck, lint, and evi tests all pass.
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
1 participant
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.
What and why
The Linear connection's tool allowlist in
apps/evi/agent/connections/linear.tsdeliberately excluded initiative writes, so the agent can only read and comment on initiatives. This addssave_initiativeso Evi can create and edit initiatives (name, description, status, dates).Linear's hosted MCP (
https://mcp.linear.app/mcp) follows a unifiedsave_<entity>convention for create-or-update writes (save_issue,save_comment,save_documentare already allowed), and its February 2026 changelog confirms initiative support was added. The connection description is updated to match.Deletes and structural writes for projects and releases remain excluded.
Why
save_initiative_updateis NOT includedThe first draft of this PR also added
save_initiative_update. It was dropped: the name is unverified against the live server, and the evidence is against it.mcp.linear.app(May 2026,tools/list) shows the analogous project-update tool does not exist there, and no public catalogue listssave_initiative_update.tools/listcall (Linear's docs confirm a personal API key works as the bearer token). I could not run it from the sandbox (no token, and the connection's token is minted in production). The probe is scripted at/workspace/probe-linear-tools.shand the tool needs a write/admin-scope key, since read-only tokens expose only read tools.If a live probe confirms the real name for initiative status updates (e.g.
save_initiative_update), it can be enabled in a follow-up.Checks
pnpm run typecheck: cleanpnpm run lint: 22/22 tasks passapps/evitests: 63/63 passNo changeset: the change is confined to
apps/evi.