1. Conduid
  2. AI
  3. Starter
MCP server · AI

Starter

skeleton start of an MCP server for a person's individual workflow. focused on prompt storage.

Unclaimed Apache-2.0 last commit 7 months ago ai
53Fair

Scored 3 months ago · breakdown

About Starter

Starter is an MCP server published by muncus in the AI category: skeleton start of an MCP server for a person's individual workflow. focused on prompt storage. It has been installed 0 times through Conduid.

The repository has 1 stars and 0 forks, with the last commit 7 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx mcp-starter

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Starter

Powered by Claude · Grounded in docs

I know everything about Starter. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Personal MCP starter kit

Motivation

AI tooling is evolving rapidly, with vendors each adding their own methods of "configuring" their models - various different markdown files like CLAUDE.md, GEMINI.md and the slightly more generic AGENTS.md. These methods work well for consistent setup across multiple developers, for a single project. This repo explores the idea of encapsulating your individual workflow as a developer as a set of MCP utilities (mostly prompts), in a way that is portable between AI tools.

Overview

This repo contains a Go MCP server that includes all prompts in the prompts/ directory, embedded in the binary itself - no need to copy around other files!

Prompts require a bit of YAML frontmatter, a name attribute at a minimum, and the remainder of the document is used as the prompt text. There are a few examples provided you can use for inspiration.

Because the prompts are embedded in the binary, updating prompts requires you to rebuild the binary. This also means that your prompts can be stored in version control, and you can determine the version of the prompts from the build data included in the binary.

Usage

  1. Clone this repo

  2. Add or edit files in prompts to suit your use case

  3. run go build . - you now have an MCP server

  4. Configure your AI tools to access this MCP server. Configs vary, but it might look something like this:

    "mcpServers": {
        "personal": {
            "command": "/path/to/your/mcp-starter"
        }
    }
    

Your prompts are now available in your AI tool of choice. They can be shared across multiple tools, too!

Why MCP?

With so many available configuration methods, why did I choose MCP?

For me, the major reason is flexibility. AI tools are changing rapidly, with a new tool or model emerging every week. To remain agile and avoid lock-in, I want to be able to use the same tools in any AI system. Today, the "greatest common factor" among AI tools is MCP. The protocol may not be ideal, but it is supported everywhere, and is one of the few standards in a rapidly evolving space.

README mirrored from the source repository 3 months ago. The original is authoritative.

Questions

About Starter

How do I install Starter?

Run npx mcp-starter, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Starter safe to use with an AI agent?

Its trust score is 53 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Starter still maintained?

The last commit was 7 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.