Skip to main content
Glama
litoralcreativo

Informix MCP Server

README.md
# Informix MCP Server

An MCP (Model Context Protocol) server for interacting with Informix databases.

## Features

- šŸ” **Database exploration**: Lists all available databases
- šŸ“Š **Table information**: Gets table details including columns and data types
- ⚔ **Custom queries**: Executes custom SQL queries
- šŸ”— **Connection testing**: Verifies database connectivity

## Installation

1. Clone this repository:
```bash
git clone <repository-url>
cd informix-mcp
```

2. Install dependencies:
```bash
npm install
```

## Usage

### Development
```bash
npm run dev
```

### Production
```bash
npm run start
```

## Available Tools

### `get-tables`
Gets all tables in a specific database.

**Parameters:**
- `database` (string): Database name

**Usage example:**
```javascript
// Get tables from database 'mydb'
const tables = await mcp.callTool("get-tables", { database: "mydb" });
```

## Configuration

To use this server with a real Informix database, you'll need to:

1. Install an Informix driver for Node.js
2. Configure connection credentials
3. Implement connection logic in the server

### Recommended Drivers

- `node-odbc` with Informix ODBC driver
- `ibm_db` (official IBM driver)
- `informix` (third-party driver)

## Development

### Project Structure

```
informix-mcp/
ā”œā”€ā”€ main.ts                 # Main MCP server
ā”œā”€ā”€ package.json           # Dependencies and scripts
ā”œā”€ā”€ tsconfig.json          # TypeScript configuration
└── README.md             # Documentation
```

## License

ISC 

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get-tables' has a clearly distinct and singular purpose, making it impossible for an agent to misselect between multiple options.

Naming Consistency5/5

The naming follows a consistent verb_noun pattern with 'get-tables', and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable within this minimal set.

Tool Count2/5

A single tool for a database server is too few for the apparent scope, as it lacks basic CRUD operations, querying, or other database management functions. This severely limits the server's utility and feels incomplete for a database domain.

Completeness1/5

The tool surface is severely incomplete for a database server, covering only table listing without any operations for data retrieval, insertion, updates, deletions, schema modifications, or other essential database interactions. This creates significant gaps that will cause agent failures in typical database workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues