FinCraftly

com.fincraftlyPublished by fincraftly.comOfficial publisherv1.0.0Updated Oct 24, 2026

AI employees that run your CRM, invoicing, email, documents, dashboards and agents

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

FinCraftly is a remote MCP endpoint offering AI employees that run CRM, invoicing, email, documents, dashboards and agents.

What you can do
Run CRM work through AI employees, per the description's mention of CRM alongside invoicing, email, documents, dashboards and agents. The listing names no individual tools, so the exact operations an assistant can call are not documented here. It is a hosted remote endpoint rather than a local package.
When to use it
Consider it if you want an assistant to handle business operations such as CRM, invoicing, email and document work through a hosted service, and you are comfortable relying on the provider's own documentation for the actual tool set.
Requirements
A remote MCP client connecting to the provider's hosted endpoint over streamable HTTP. The manifest declares no authentication, environment variables or headers, and no packages; confirm with the provider what account or access setup is actually needed.
Before you install
The description implies write access to business records such as CRM data, invoices, email and documents, so actions may create, send or change data. No authentication is declared, which is unusual for business data; verify access control and how your data is handled before connecting.

Installation

In SourceWeft

  1. Open FinCraftly in the dashboard and add it to a workspace.
  2. 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.fincraftly%2Fworkforce/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.

{
  "mcpServers": {
    "fincraftly": {
      "type": "http",
      "url": "https://fincraftly.com/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

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

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