Skip to main content
Glama

FinCraftly

by com.fincraftly
OverviewDiscussionsAdmin

Server Details

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

Ownership verified

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
32.0% over 21 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

A3.6/5.0

Scored across 30 tools

Disambiguation3/5

Descriptions work hard to demarcate boundaries (employee vs agent, shortcut vs fincraftly_mutate), which mitigates a lot of overlap. However, generic fincraftly_query/finecraftly_mutate clearly overlap with the many list_*/create_* shortcuts, and fincraftly_get_state vs fincraftly_get_org_context both return workforce summaries that are easy to confuse.

Naming Consistency4/5

All tools share the fincraftly_ prefix and snake_case, and most follow a verb_noun pattern (create_invoice, list_contacts, send_email). A few generic/meta tools (describe, batch, mutate, query, integrations_context) deviate from verb_noun but remain readable and consistent.

Tool Count3/5

30 tools is heavy for a single server. The domain is genuinely broad (workforce, CRM, invoices, dashboards, integrations, email), but several convenience create_*/list_* tools are partially redundant given the generic query/mutate pattern, making the set feel borderline bloated.

Completeness5/5

The generic fincraftly_query and fincraftly_mutate provide read/write access across all workspace entities, and fincraftly_describe exposes the full action map with schemas, so CRUD and lifecycle coverage is effectively complete. Discovery, batch, integrations, workforce, CRM, invoicing, and output tools round out the surface with no obvious dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Changedfincraftly_batch1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "description": "Per-call results in order, with counts. On a stop, `stopped_at` and `not_run` say where it halted and how many calls never ran.",
+  "properties": {
+    "completed": {
+      "type": "number"
+    },
+    "failed": {
+      "type": "number"
+    },
+    "not_run": {
+      "type": "number"
+    },
+    "results": {
+      "type": "array"
+    },
+    "stopped_at": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
    • Changedfincraftly_describe1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "A catalogue view: the area overview, the actions in one area with their input schemas, one action in full, or search hits. The exact keys depend on the arguments.",
+  "type": "object"
+}
    • Changedfincraftly_mutate1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "description": "The write result. `data` is the endpoint payload; `status` is its status; `replayed` is true when an idempotency key returned an earlier result instead of writing again.",
+  "properties": {
+    "action": {
+      "type": "string"
+    },
+    "data": {},
+    "replayed": {
+      "type": "boolean"
+    },
+    "status": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "action",
+    "status",
+    "data"
+  ],
+  "type": "object"
+}
    • Changedfincraftly_query1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "description": "The read result. `data` is the endpoint payload (an object, or a list for list actions); `action` and `status` identify the call, and `pagination` is present on list endpoints.",
+  "properties": {
+    "action": {
+      "type": "string"
+    },
+    "data": {},
+    "pagination": {
+      "type": "object"
+    },
+    "status": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "action",
+    "status",
+    "data"
+  ],
+  "type": "object"
+}
  2. 30 tool updates
    • First observedfincraftly_add_employee
    • First observedfincraftly_assign_manager
    • First observedfincraftly_batch
    • First observedfincraftly_call_api
    • First observedfincraftly_call_mcp_tool
    • First observedfincraftly_create_agent
    • First observedfincraftly_create_contact
    • First observedfincraftly_create_customer
    • First observedfincraftly_create_dashboard
    • First observedfincraftly_create_department
    • First observedfincraftly_create_invoice
    • First observedfincraftly_describe
    • First observedfincraftly_design_department
    • First observedfincraftly_get_org_context
    • First observedfincraftly_get_state
    • First observedfincraftly_integrations_context
    • First observedfincraftly_list_apis
    • First observedfincraftly_list_contacts
    • First observedfincraftly_list_dashboards
    • First observedfincraftly_list_invoices
    • First observedfincraftly_list_mcp_tools
    • First observedfincraftly_list_mcps
    • First observedfincraftly_list_outputs
    • First observedfincraftly_list_tasks
    • First observedfincraftly_mutate
    • First observedfincraftly_present_output
    • First observedfincraftly_query
    • First observedfincraftly_route_task
    • First observedfincraftly_send_email
    • First observedfincraftly_send_invoice

Publisher details

Operator
FinCraftly · Publisher source
Operator website
https://fincraftly.com · Publisher source
Vendor relationship
First-party · Publisher source
Documentation
https://fincraftly.com/documentation · Publisher source
Trust center
Not available
Restrictions
Requires a FinCraftly account and OAuth 2.0 sign-in. An access token is currently required on every request, including initialize and tools/list, so the tool list cannot be read before authenticating. Dynamic client registration is supported, so no custom OAuth app is needed. · Publisher source

Related MCP Connectors

Related MCP Servers

  • Airtable MCP Server

    Pavansaigudla
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI clients to securely search, create, update, and delete employee records in a base, including advanced filtering by department, status, designation, or ID, along with duplicate ID and email validation. It also provides dashboard statistics for employees through natural language tools.
    2,582 npm
    1
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources