Skip to main content
Glama
finamatik

Ops MCP Server (Finamatik)

Official
by finamatik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Ops MCP Server (Finamatik)

No user-submitted related servers found.

    Related Servers

    • MCPServer

      Bhanuprakashdadi145
      F
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server built with Python, exposing 17 tools to manage users, products, and orders via a JSON-backed REST API, ready for Claude Desktop and any MCP client.
      -

    • CRM Agent Tools

      PureGit90
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides Claude agents with CRM contact lookup, action logging, and prompt cost auditing tools. Includes a Streamlit UI to demo the same tools without an MCP client.
      -

    • agent-crm

      clayton
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage CRM data including companies, contacts, prospects, pipelines, forecasts, and tasks via typed MCP tools, with local SQLite storage and a JSON CLI.
      MIT

    • FutureSense MCP

      Sams3595
      A
      license
      Not graded
      quality
      D
      maintenance
      556-tool MCP server giving AI agents full access to the FutureSense business platform. Covers 10 app domains: invoicing, payroll, accounting, CRM, booking, content creation, website builder, quotations, email, and more. Works with Claude, ChatGPT, Gemini, Cursor, and any MCP-compatible client.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search vs. full profile lookup (search_contacts/get_contact), task listing vs. creation vs. completion, and inventory, pipeline, note, and order operations are all separate concerns. The only near-overlap (check_inventory vs. create_order stock check) is explicitly clarified in the descriptions.

    Naming Consistency4/5

    Most tools follow a clean verb_noun pattern (search_contacts, get_contact, list_tasks, add_note, create_task, complete_task, update_deal_stage, create_order). The single outlier is pipeline_summary, which is noun-only with no verb, a minor deviation from an otherwise consistent convention.

    Tool Count5/5

    Ten tools is well within the ideal 3-15 range and each one covers a distinct operational need for a CRM/ops assistant. No tool feels redundant or padded.

    Completeness3/5

    Tasks have list/create/complete but no update or delete, contacts can only be read (no create/update), and orders/deals lack listing or retrieval tools (e.g. no list_orders, get_deal, delete task). Core read workflows exist but the lifecycle surface has notable gaps that could cause dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources