Eclipse Apply MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 26, 2026

The auto-apply tool that shows its work — policy-scoped autonomy, review-first, receipts for

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Eclipse Apply MCP is a local, desktop-only auto-apply tool that lets an assistant submit applications under policy-scoped autonomy, with review-first steps…

What you can do
  • The listing names no tools, so capabilities are known only from the description.
  • It is presented as an auto-apply tool that shows its work.
  • Autonomy is described as policy-scoped, with a review-first flow.
  • It is said to produce receipts for its actions.
When to use it
Consider it when you want an assistant to help submit applications automatically while keeping actions bounded by a policy and reviewed before they go out. The sparse listing makes it hard to judge fit without checking the vendor's own documentation.
Requirements
Runs as a local process on the user's machine over stdio, desktop only; no web executable. No packages, authentication, environment variables or headers are declared, so the actual runtime and any account needs are not stated.
Before you install
It is described as an auto-apply tool, so it may submit applications on your behalf; the review-first and policy-scoped design is claimed but not documented here. No credentials, data handling or third-party recipients are disclosed, so verify these before installing.

Installation

In SourceWeft

  1. Open Eclipse Apply MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 26, 2026

Score

25% 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 days25 pts

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

  • Auth declared10 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.

  • License10 pts

    Declare a license in the repository or the registry entry.