griffin

Griffin MCP server provides an interface to interact with the Griffin API through MCP clients. Once running, you can query and manage Griffin resources such as bank accounts, payments, legal persons, payees, and transactions using the built-in tools exposed by the server. The server supports a range of commands like creating and submitting payments, opening or closing accounts, listing resources, and fetching detailed information about specific resources. It is designed to be used with MCP clients such as Claude Desktop or code editors that support MCP, enabling automated workflows and conversational interactions with Griffin data.

To use it with Claude Desktop (or other MCP clients), configure the mcpServers section in your client and provide your Griffin API key via the GRIFFIN_API_KEY environment variable. The server runs via npx @griffinbank/mcp-server and reads the API key from the environment to authenticate requests. Once configured, you can invoke commands such as creating a payment, listing bank accounts, or retrieving details about a legal person or transaction through the MCP client’s command palette or scripting interface.

Prerequisites:

• Node.js v16 or later
• npm v7 or later
• A Griffin API Key (obtain from app.griffin.com/register)

Install and run the MCP server using npx (no global install required):

# Ensure Node.js and npm are installed
node -v
npm -v

# Run the Griffin MCP server via npx (as shown in the README guidance)
npx -y @griffinbank/mcp-server

Configure your MCP client (e.g., Claude Desktop) to point to the Griffin MCP server with the required API key in the environment:

{
  "mcpServers": {
    "griffin": {
      "command": "npx",
      "args": ["-y", "@griffinbank/mcp-server"],
      "env": {
        "GRIFFIN_API_KEY": "your-griffin-api-key"
      }
    }
  }
}

If you prefer a local run without a client, you can also install the package directly (if available as a local dependency) and run it with Node.js, but the recommended approach is through npx as shown above.

Tips and considerations:

• Never expose your Griffin API key in public repositories or shared configurations. Use environment variables and keep keys secure.
• The MCP server keys off the GRIFFIN_API_KEY env var; ensure it is set in the environment where the server runs.
• If you see authentication or network errors, verify your API key is valid and that your network can reach Griffin services.
• This server is labeled beta; test workflows thoroughly before using them in production.
• When configuring clients like Claude Desktop, ensure the mcpServers section aligns with the client’s config format and that the client restarts after changes.
• You can leverage the provided tools to manage banks, payments, and related resources programmatically via your MCP client.