Scope-gated Linear project administration with optional GitHub and Obsidian evidence adapters
MCPpedia last refreshed this data
org.openlyuseful/linear-project is an MCP server that scope-gated Linear project administration with optional GitHub and Obsidian evidence adapters. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"org-openlyuseful-linear-project": {
"args": [
"-y",
"@openly-useful/linear-project-mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Three interoperable Agent Skills and an optional MCP server for creating, maintaining, and reconciling Linear projects without pulling unrelated work into scope.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@openly-useful/linear-project-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @openly-useful/linear-project-mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Local-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free.
MCP server for monday.com integration.
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
An MCP server to extend the context of agents. Useful when coding big features or vibe coding and need to store/recall progress, key moments or changes or anything worth remembering. Simply ask the agent to store memories and recall whenever you want.
MCP Security Weekly
Get CVE alerts and security updates for org.openlyuseful/linear-project and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Three interoperable Agent Skills and an optional MCP server for creating, maintaining, and reconciling Linear projects without pulling unrelated work into scope.
This collection is an Openly Useful project: practical infrastructure people can inspect, adapt, and improve.
Openly Useful LLC is the planned legal entity and remains formation-pending. Openly Useful is currently operated by its founder as an individual, and this repository does not claim that the LLC is formed, active, or the current operator. publisher.json is a repo-local projection of the public publisher authority. The founder-owner has authorized external source and registry publication while formation proceeds; namespace verification, provider authentication, and provider review remain provider-specific steps.
| Skill | Use it to |
|---|---|
linear-bootstrap-scoped-project | Create a net-new project, establish the key-bearing team, link canonical sources, and import legacy work safely. |
linear-sync-project-work | Keep implementation evidence, backlog gaps, blockers, and status current while work proceeds. |
linear-reconcile-project-history | Find an existing project, move high-confidence related issues, and capture legacy evidence as [HISTORICAL]. |
The skills hand work to one another rather than duplicating responsibilities:
new project ──> bootstrap ──> sync
▲
│ no canonical project
existing work ─> reconcile ──> sync
@openly-useful/linear-project-mcp-server turns the workflows into 13 typed MCP tools. It can create a dedicated Linear team or subteam, bootstrap a scope-labeled project, capture active or [HISTORICAL] issues idempotently, find and explicitly move reviewed reconciliation candidates, and link verified evidence.
The server calls Linear directly through its official TypeScript SDK. GitHub evidence is optional and read-only. Obsidian support is optional, local, restricted to allowlisted Markdown directories, and never copies note contents into Linear when adding a link.
All mutations are disabled by default and require an exact organization allowlist, a scope-code allowlist, team/project gates, and a literal per-tool confirmation. See the server setup and security guide for installation and client configuration.
The MCP integration has four intentionally distinct names:
| Name | Meaning |
|---|---|
linear_project | Canonical Codex MCP registration alias and the name used with codex mcp commands. |
@openly-useful/linear-project-mcp-server | npm package name. It becomes installable from npm after the first successful package release. |
linear-project-mcp-server | Package executable and MCP protocol server artifact name. |
linear-project-mcp-write-window | Package helper for explicitly opening, inspecting, and closing a bounded write window. |
For a source checkout, build the package and register the local executable with Codex:
cd mcp/linear-project-mcp-server
pnpm install --frozen-lockfile
pnpm build
MCP_ENTRYPOINT="$(pwd)/dist/index.js"
codex mcp add linear_project -- node "$MCP_ENTRYPOINT"
codex mcp get linear_project --json
codex mcp list --json
These commands contain no credentials. Supply adapter credentials through a protected launcher or secret store rather than command arguments or committed client configuration. See the MCP client guide for the npm command that applies after the first release and for the expected read-only acceptance checks.
Linear issu