Project Intake Identifier

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.0.7Updated Oct 8, 2026

Prepare project context from an intake note

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP endpoint that prepares project context from an intake note.

What you can do
This server is described as preparing project context from an intake note. The registry entry gives only that one-line purpose; no tool list, parameters, or output format are published, so the exact operations it exposes are not documented. It runs as a remote streamable HTTP endpoint rather than a local package.
When to use it
Consider it when you want an assistant to turn a short project intake note into usable project context, for example at the start of scoping or kickoff work. Because no tools or behavior are documented, treat it as an experiment rather than a dependable part of a workflow.
Requirements
Nothing is declared: no packages, environment variables, headers, or authentication. It is a remote endpoint, so the assistant needs network access to the provider's URL. No account or API key is stated as required.
Before you install
The endpoint is hosted on a temporary-looking cloudflare tunnel address, which may change or disappear without notice. No authentication is declared, so anything sent to it may be handled without access control, and the intake notes you submit could contain confidential project details. No tool list is published, so what it does with your input cannot be verified in advance.

Installation

In SourceWeft

  1. Open Project Intake Identifier in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Wxt-ai%2Fproject-intake-identifier/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "project-intake-identifier": {
      "type": "http",
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/project-intake-identifier"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.7LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.