Mifosx

Mifosx avatar

by openMF

mifosxmodel-context-protocolBrowser Automation

What is Mifosx

Mifos X - AI - Model Context Protocol (MCP)

Use

In your AI agent tool (ChatGPT, Google AI Studio, Claude Desktop) add this MCP configuration

{
    "mcpServers": {
        "mifosx": {
            "command": "jbang",
            "args": ["--quiet",
                    "org.mifos.community.ai.mcp:mcp-server:1.0.0-SNAPSHOT:runner"],
             "env":{
				"MIFOSX_BASE_URL":"",
				"MIFOSX_BASIC_AUTH_TOKEN":"",
				"MIFOS_TENANT_ID":""
             }
        }
    }
}

Introduction

This project uses Quarkus, the Supersonic Subatomic Java Framework.

If you want to learn more about Quarkus, please visit its website: https://quarkus.io/.

Running the application in dev mode

You can run your application in dev mode that enables live coding using:

./mvnw quarkus:dev

NOTE: Quarkus now ships with a Dev UI, which is available in dev mode only at http://localhost:8080/q/dev/.

Packaging and running the application

The application can be packaged using:

./mvnw package

It produces the quarkus-run.jar file in the target/quarkus-app/ directory. Be aware that it’s not an über-jar as the dependencies are copied into the target/quarkus-app/lib/ directory.

The application is now runnable using java -jar target/quarkus-app/quarkus-run.jar.

If you want to build an über-jar, execute the following command:

./mvnw package -Dquarkus.package.jar.type=uber-jar

The application, packaged as an über-jar, is now runnable using java -jar target/*-runner.jar.

Creating a native executable

You can create a native executable using:

./mvnw package -Dnative

Or, if you don't have GraalVM installed, you can run the native executable build in a container using:

./mvnw package -Dnative -Dquarkus.native.container-build=true

You can then execute your native executable with: ./target/mcp-server-1.0.0-SNAPSHOT-runner

If you want to learn more about building native executables, please consult https://quarkus.io/guides/maven-tooling.

Related Guides

  • Qute (guide): Offer templating support for web, email, etc in a build time, type-safe way
  • Model Context Protocol (MCP) Server for standard input/output (stdio) (guide): This extension enables developers to implement the MCP server features easily using stanard input/output (stdio).

MCP Developer Tools

For development and testing, you can use the MCP Inspector tool:

npx @modelcontextprotocol/inspector

This starts a local web server where you can test your MCP server and you can connect it using STDIO or SSE

Leave a Comment

Comments section will be available soon. Stay tuned!

Frequently Asked Questions

What is MCP?

MCP (Model Context Protocol) is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications, providing a standardized way to connect AI models to different data sources and tools.

What are MCP Servers?

MCP Servers are lightweight programs that expose specific capabilities through the standardized Model Context Protocol. They act as bridges between LLMs like Claude and various data sources or services, allowing secure access to files, databases, APIs, and other resources.

How do MCP Servers work?

MCP Servers follow a client-server architecture where a host application (like Claude Desktop) connects to multiple servers. Each server provides specific functionality through standardized endpoints and protocols, enabling Claude to access data and perform actions through the standardized protocol.

Are MCP Servers secure?

Yes, MCP Servers are designed with security in mind. They run locally with explicit configuration and permissions, require user approval for actions, and include built-in security features to prevent unauthorized access and ensure data privacy.