First100

io.github.jpalepuPublished by GitHub account jpalepuv2.2.0Updated Oct 24, 2026

Go-to-market tools for AI agents: publish and schedule posts, find customers, SEO, outreach.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Go-to-market tooling that lets an assistant publish and schedule posts, find customers, handle SEO and run outreach.

What you can do
This server exposes go-to-market capabilities to an AI assistant. According to the registry description, it covers publishing and scheduling posts, finding customers, SEO work and outreach. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Worth considering when you want an assistant to help with marketing and sales tasks such as drafting and scheduling social posts, identifying potential customers, improving search visibility, or running outreach campaigns. It is aimed at go-to-market work rather than general development or data tasks. Because the tool list is not published, review the available operations before relying on it for anything that sends messages or publishes content.
Requirements
A remote endpoint at or a local process installed from the npm package first100-mcp over stdio. Authentication is required via OAuth, and credentials are supplied as the environment variable FIRST100_API_KEY or the Authorization header. An API key is obtained from the provider's dashboard. Network access is needed.
Before you install
The server requires credentials: the environment variable FIRST100_API_KEY and the Authorization header, both described as secrets. Treat them as sensitive and avoid exposing them in logs or shared configuration. The tools themselves are not listed in the manifest, so confirm what actions the server can take, in particular whether it can publish or schedule posts and send outreach messages on your behalf, before granting access.

Installation

In SourceWeft

  1. Open First100 in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.jpalepu%2Ffirst100/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "first100": {
      "type": "http",
      "url": "https://firsthundred.app/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.2.0LatestSep 16, 2026

Score

60% 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
  • Auth declaredRequired10 pts
  • 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.