FIMA MCP

com.tryfimaPublished by tryfima.comOfficial publisherv0.1.0Updated Oct 29, 2026

Read-only financial reports for projects the authenticated FIMA user is authorized to access.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server that gives an assistant read-only access to financial reports for FIMA projects the signed-in user is authorized to see.

What you can do
  • Retrieve financial reports for FIMA projects the authenticated user is permitted to access.
  • Access is read-only, so the assistant can look up and summarize report data without changing anything.
  • Results are limited to the projects tied to the signed-in FIMA account.
When to use it
Useful when you work in FIMA and want an assistant to pull or summarize financial reports for your projects without leaving the chat. It fits read-only reporting questions rather than editing or bookkeeping tasks.
Requirements
A remote MCP endpoint at mcp.tryfima.com, reachable over streamable HTTP. OAuth sign-in with a FIMA account is required; no environment variables or headers are declared.
Before you install
Sign-in grants the assistant access to financial reports for every project your FIMA account is authorized for, so review that scope before connecting. Report data is served by a third-party service over the network.

Installation

In SourceWeft

  1. Open FIMA 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.tryfima%2Ffima-mcp/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": {
    "fima": {
      "type": "http",
      "url": "https://mcp.tryfima.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. v0.1.0LatestOct 29, 2026

Score

67% 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.

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