Project Intake Identifier

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.3.0Updated Oct 15, 2026

Prepare project context from an intake note.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP endpoint that prepares project context from an intake note, giving an assistant a starting point for project setup.

What you can do
  • Prepares project context from an intake note.
  • No tool list, instructions or README are published, so the exact operations and their inputs cannot be confirmed from the listing.
When to use it
Consider it when you have an intake note and want an assistant to turn it into project context before starting work. Because the published details are minimal, verify what it actually does before relying on it.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. No authentication is declared, so nothing needs to be configured for access.
Before you install
The endpoint is a temporary-looking cloudflare tunnel host, which may change or disappear. No authentication is declared, so anything sent to it is not protected by credentials, and the intake note content is passed to a third-party service. No tool list is published, so review its behavior before sending sensitive project details.

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-code-notes-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://determination-unlimited-consultancy-spy.trycloudflare.com/mcp/project-code-notes-identifier"
    }
  }
}

Tools

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

Version history

3
  1. v1.3.0LatestOct 15, 2026
  2. v1.1.1Oct 7, 2026
  3. v1.0.4Sep 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.