Autoplans Mcp

io.github.mohamedgb00714Published by GitHub account mohamedgb00714v0.1.2Updated Oct 24, 2026

AI-powered project planning tools for Autoplans.dev with 14+ MCP tools

VerifiedSTDIODesktop onlyProductivity & Workflow

Server details

Identifier: io.github.mohamedgb00714/autoplans-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account mohamedgb00714 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.mohamedgb00714%2Fautoplans-mcp.svg)](https://sourceweft.com/mcp/io.github.mohamedgb00714%2Fautoplans-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that connects an AI assistant to Autoplans.dev, giving it AI-powered project planning tools.

What you can do: Provides AI-powered project planning capabilities for Autoplans.dev, exposed to the assistant as a set of MCP tools (the description mentions 14 or more). The manifest does not list the individual tools, so the exact actions available are not documented here.
When to use it: Worth considering if you already use Autoplans.dev for project planning and want an assistant to work with it directly from a desktop MCP client.
Requirements: Runs as a local process over stdio, installed from the npm package autoplans-mcp, so Node.js and a desktop MCP client are needed. Requires an Autoplans.dev API key supplied in the AUTOPLANS_API_KEY environment variable.

Before you install

The server needs an Autoplans.dev API key; keep it out of shared configuration and logs. The tool list is not published, so what the assistant can read or change in your Autoplans.dev account is unclear; review before use. Planning data is sent to the Autoplans.dev service.

Installation

In SourceWeft

Open Autoplans Mcp in the dashboard and add it to a workspace.
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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

v0.1.2LatestSep 16, 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.