First AI Employee

io.github.Strah0taPublished by GitHub account Strah0tav1.0.1Updated Nov 11, 2026

AI receptionist business records and approved front-desk workflows. OAuth sign-in required.

The publisher's own server: First

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that gives an assistant access to an AI receptionist's business records and approved front-desk workflows.

What you can do
  • Access AI receptionist business records
  • Run approved front-desk workflows
  • No tool list is published, so specific operations are not documented
When to use it
Useful if you already rely on this AI receptionist service and want an assistant to work with its business records and front-desk workflows.
Requirements
Remote endpoint at api.firstaiemployee.com over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
OAuth grants access to business records and front-desk workflows, which may include customer data and actions that change records; review the scopes granted during sign-in. No tool list is published, so what the assistant can read or change is not documented here.

Installation

In SourceWeft

  1. Open First AI Employee 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.Strah0ta%2Ffirst-ai-employee/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": {
    "first-ai-employee": {
      "type": "http",
      "url": "https://api.firstaiemployee.com/mcp"
    }
  }
}

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. v1.0.1LatestNov 11, 2026

Score

83% 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
  • 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.

Other First integrations