Project Intake Identifier
by io.github.Wxt-ai · ai-ml · mcp-server, official-registry
Identify the project handle from an intake note
Tags: mcp-server, official-registry
Source: mcp-registry
About ai-ml MCP servers and Claude skills
ai-ml MCP servers extend what AI agents can do inside Claude Code, Cursor, Copilot, Codex, and Windsurf. The Skiln directory indexes 16,000+ such integrations across 22 categories.
Project Intake Identifier is one of hundreds of ai-ml entries indexed on Skiln. Browse the full ai-ml category or the complete directory of Claude skills, MCP servers, agents, commands, and hooks.
Related ai-ml MCPs and skills
- Workspace Publication Queue by io.github.Wxt-ai
Queue a workspace publication path
- Knowledge Placement Planner by io.github.Wxt-ai
Plan a knowledge-base placement path
- Operations Activity Ledger by io.github.Wxt-ai
Append an operations activity entry
- Knowledge Evidence Finder by io.github.Wxt-ai
Find the reference marker for a knowledge item
- Operations Schedule Console by io.github.Wxt-ai
Schedule an operations task
- Capacity Queue Planner by io.github.Wxt-ai
Plan capacity handling for a task
- Support Case Workbench by io.github.Wxt-ai
Add a support case follow-up
- Support Intake Digest by io.github.Wxt-ai
Digest a support intake marker
Frequently asked questions
How do I install Project Intake Identifier?
Add the install command above to your Claude Code, Cursor, or Windsurf MCP configuration. Most servers register via npx, a local command, or a Docker image. Refer to the upstream documentation for environment variables and credential requirements.
Which clients support Project Intake Identifier?
Any MCP-compatible client works: Claude Desktop, Claude Code CLI, Cursor, Windsurf, Zed, and VS Code with the official MCP extension. OpenAI Codex and GitHub Copilot increasingly support MCP via adapter bridges.
Is Project Intake Identifier free?
The server itself is typically open source. Any upstream service (API keys, paid tiers, hosted infrastructure) may have its own pricing. Check the source repository for details.