ClientFoyer MCP

com.clientfoyerPublished by clientfoyer.comOfficial publisherv1.1.0Updated Oct 29, 2026

ClientFoyer MCP server for a freelancer client portal - projects, updates, files, invoices.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for a freelancer client portal, giving an assistant access to projects, updates, files and invoices.

What you can do
  • Work with client portal projects and their updates
  • Access files shared through the portal
  • Handle invoices associated with client work
  • No individual tools are documented, so the exact actions available are not specified.
When to use it
Worth considering if you run a freelance or client-facing practice on ClientFoyer and want an assistant to work with portal projects, updates, files and invoices without switching apps.
Requirements
A remote endpoint at clientfoyer.com over streamable HTTP; no local package or runtime. Authentication is OAuth and required, so a ClientFoyer account is needed. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in to your ClientFoyer account, so the assistant acts with your portal permissions. It covers invoices and client files, which are sensitive business and customer data; check what the assistant can read or change before connecting. No tool list is published, so the scope of write actions is unclear.

Installation

In SourceWeft

  1. Open ClientFoyer MCP 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/com.clientfoyer%2Fclientfoyer/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": {
    "clientfoyer": {
      "type": "http",
      "url": "https://clientfoyer.com/api/v1/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v1.1.0LatestOct 29, 2026
  2. v1.0.0Oct 26, 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.