Aifp

Database-driven FP enforcement and project management for AI-maintained codebases

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "aifp": {
      "command": "uvx",
      "args": [
        "aimfp@latest"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

AIMFP: AI Modular Functional Procedural Programming

A language-agnostic programming paradigm designed for AI-generated and AI-maintained codebases

What is AIMFP?
Core Principles
Architecture Overview
Database Architecture
How It Works
Getting Started
Platform Support
Directives System
Project Lifecycle
Example Workflow
Documentation
Development
Design Philosophy
Features
Usage Examples
Privacy Policy
Support
License

What is AIMFP?

AIMFP (AI Modular Functional Procedural) is a programming paradigm that combines:

Pure functional programming principles (referential transparency, immutability, composability)
Procedural execution patterns (explicit sequencing, no hidden state)
Database-driven project management (persistent state, instant context retrieval)
Directive-based AI guidance (deterministic workflows, automated compliance)

Two Ways to Use AIMFP

Use Case 1: Regular Software Development

Build applications (web apps, libraries, CLI tools, etc.)
AIMFP enforces FP compliance and manages your project
You write code, AI assists with FP standards and project tracking
Example: Building a web server, calculator library, data processor

Use Case 2: Custom Directive Automation

Define automation rules (home automation, cloud management, workflows)
AIMFP generates and manages the automation codebase for you
You write directive definitions (YAML/JSON/TXT), AI generates the implementation
The project's code IS the automation code generated from your directives
Example: Smart home control system, AWS infrastructure manager, workflow automator

Key Principle: One AIMFP instance per project directory. You would NOT mix a web app with home automation directives. Run separate instances for separate purposes.

Why AIMFP?

Traditional programming paradigms were designed for humans. AIMFP is optimized for AI-human collaboration:

Challenge	Traditional Approach	AIMFP Solution
Context Loss	AI forgets between sessions	Database-driven persistent state
OOP Complexity	Classes, inheritance, polymorphism	Pure functions, explicit data structures
Infinite Development	Projects never "complete"	Finite completion paths with milestones
Code Reasoning	Parse source code repeatedly	Pre-indexed functions, dependencies, interactions
Inconsistent Standards	Style guides, linters, reviews	Immutable directives enforcing compliance

Core Principles

1. Functional-Procedural Hybrid

python

# ✅ AIMFP-Compliant
def calculate_total(items: List[Item]) -> float:
    """Pure function: deterministic, no side effects"""
    return reduce(lambda acc, item: acc + item.price, items, 0.0)

# ❌ Not AIMFP-Compliant
class Calculator:
    def __init__(self):
        self.total = 0  # Hidden state

    def add_item(self, item):
        self.total += item.price  # Mutation

2. Database-Indexed Logic

Every function, file, and dependency is tracked in SQLite. AI accesses this data through helper tools — not raw SQL:

Code

AI calls: get_functions_by_file(file_id)
→ Returns: all functions in that file with name, purpose, parameters, returns

No source code reparsing required. Instant context retrieval across sessions.

3. AI-Readable Code

Flat structure: No deep inheritance hierarchies
Explicit dependencies: All parameters passed explicitly
Pure functions: Same inputs → same outputs
Metadata annotations: Machine-readable function headers

4. Finite Completion Paths

Code

Project: MatrixCalculator
├── Completion Path (3 stages)
│   ├── 1. Setup (completed)
│   ├── 2. Core Development (in progress)
│   │   ├── Milestone: Matrix Operations
│   │   │   ├── Task: Implement multiply
│   │   │   ├── Task: Implement transpose
│   │   │   └── Task: Add validation
│   │   └── Milestone: Vector Operations
│   └── 3. Finalization (pending)

5. Language-Agnostic

AIMFP works with Python, JavaScript, TypeScript, Rust, Go, and more. FP directives adapt to language-specific syntax while maintaining universal standards.

Architecture Overview

Code

┌─────────────────────────────────────────────────────┐
│            AI Assistant (Claude, GPT-4, etc.)        │
│  - Receives natural language commands                │
│  - Follows directives (FP baseline + project mgmt)   │
│  - Calls MCP tools to read/write databases           │
│  - Generates FP-compliant code                       │
└────────────────────┬────────────────────────────────┘
                     │ MCP Protocol (JSON-RPC over stdio)
┌────────────────────▼────────────────────────────────┐
│                 MCP Server                           │
│  - Exposes helper tools via JSON-RPC                  │
│  - Manages four-database connections                 │
│  - Provides CRUD helpers for all databases           │
│  - No business logic — AI makes all decisions        │
└───┬────────────────────┬─────────────────────────┬──┘
    │                    │                         │
┌───▼──────────────┐ ┌───▼────────────────┐ ┌─────▼─────────────────┐ ┌──────▼────────────────┐
│  aimfp_core.db    │ │  project.db        │ │  user_preferences.db  │ │  user_directives.db   │
│  (Global,        │ │  (Per-Project,     │ │  (Per-Project,        │ │  (Per-Project,        │
│   Read-Only)     │ │   Mutable)         │ │   Mutable)            │ │   Optional)           │
│                  │ │                    │ │                       │ │                       │
│ - FP directives  │ │ - Project metadata │ │ - Directive prefs     │ │ - User directives     │
│ - Project mgmt   │ │ - Files & funcs    │ │ - User settings       │ │ - Execution stats     │
│ - User prefs     │ │ - Task hierarchy   │ │ - AI learning log     │ │ - Dependencies        │
│ - User systems   │ │ - Themes & flows   │ │ - Tracking features   │ │ - Generated code refs │
│ - Helper defs    │ │ - Completion path  │ │ (All opt-in)          │ │ - Source file tracking│
│ - Directive flow │ │ - Runtime notes    │ │                       │ │ (Logs in files)       │
└──────────────────┘ └────────────────────┘ └───────────────────────┘ └───────────────────────┘

Use Case 2 adds a second path that never touches the MCP server. Your automation has to run when no AI session is open, so it imports AIMFP as a plain library instead:

server.ts

┌──────────────────────────────┐        ┌──────────────────────────────┐
│  cron / systemd / your daemon │        │  AI Assistant (a session)     │
│  runs forever; AIMFP does not │        │  present only when you are    │
└───────────────┬──────────────┘        └───────────────┬──────────────┘
                │ starts                                 │ MCP
┌───────────────▼──────────────┐        ┌───────────────▼──────────────┐
│  runner.py  (YOUR project)    │        │         MCP Server            │
│  generated by AIMFP, owned    │        │                               │
│  and editable by you          │        │  check_directive_health       │
│                               │        │  get_directive_execution_stats│
│  import aimfp.hooks  ◄────────┼── a    │  get_recent_directive_errors  │
│  get_due_directives(...)      │  library                              │
│  run_directive(...)           │  call, └───────────────┬──────────────┘
└───────────────┬──────────────┘  not RPC               │ reads
                │ writes                                 │
                └────────────►  user_directives.db  ◄────┘
                                + .aimfp-project/logs/

The runner writes; the AI reads it back later. AIMFP itself is inert in between — it has no timer and starts nothing.

Database Architecture

aimfp_core.db (Global, Read-Only)

Location: Within MCP server installation directory (user-defined location, configured in AI client)

Purpose: Immutable knowledge base containing all AIMFP standards, directives, and helper definitions.

Key Tables:

directives: All FP, project, and user preference directives (workflows, keywords, thresholds)
helper_functions: Database, file, Git, and FP utilities organized across multiple registry files
directive_helpers: Many-to-many junction table mapping directives to their helper functions with execution metadata
categories: Directive groupings (purity, immutability, task management, etc.)
directive_flow: Status-driven directive navigation and routing

Helper-Directive Relationship (New in v1.4):

One directive can use many helpers, one helper can serve many directives
Junction table stores: execution context, sequence order, parameter mappings
Enables flexible helper reuse and clear execution flow
Defined in directive_helpers junction table in aimfp_core.db

Helper Classification:

Tool: All helpers are exposed as MCP tools (AI calls directly via MCP)
Sub-helper (is_sub_helper = TRUE): Internal utility called by other helpers only (not exposed to AI)

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit

1mo ago

Most recent push to the default branch.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Aifp

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "aifp": { "command": "uvx", "args": ["aimfp@latest"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/aifp?style=directory)](https://allmcps.com/mcp/aifp)

HTML Embed

<a href="https://allmcps.com/mcp/aifp"><img src="https://allmcps.com/api/badge/aifp?style=directory" alt="Aifp on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

1/5 checks healthy over the last 46d

37Quality signal: Fair · 37/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity2/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · aimfp@latest (PyPI)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Aifp →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

Aifp

Database-driven FP enforcement and project management for AI-maintained codebases

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "aifp": {
      "command": "uvx",
      "args": [
        "aimfp@latest"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

AIMFP: AI Modular Functional Procedural Programming

A language-agnostic programming paradigm designed for AI-generated and AI-maintained codebases

What is AIMFP?
Core Principles
Architecture Overview
Database Architecture
How It Works
Getting Started
Platform Support
Directives System
Project Lifecycle
Example Workflow
Documentation
Development
Design Philosophy
Features
Usage Examples
Privacy Policy
Support
License

What is AIMFP?

AIMFP (AI Modular Functional Procedural) is a programming paradigm that combines:

Pure functional programming principles (referential transparency, immutability, composability)
Procedural execution patterns (explicit sequencing, no hidden state)
Database-driven project management (persistent state, instant context retrieval)
Directive-based AI guidance (deterministic workflows, automated compliance)

Two Ways to Use AIMFP

Use Case 1: Regular Software Development

Build applications (web apps, libraries, CLI tools, etc.)
AIMFP enforces FP compliance and manages your project
You write code, AI assists with FP standards and project tracking
Example: Building a web server, calculator library, data processor

Use Case 2: Custom Directive Automation

Define automation rules (home automation, cloud management, workflows)
AIMFP generates and manages the automation codebase for you
You write directive definitions (YAML/JSON/TXT), AI generates the implementation
The project's code IS the automation code generated from your directives
Example: Smart home control system, AWS infrastructure manager, workflow automator

Key Principle: One AIMFP instance per project directory. You would NOT mix a web app with home automation directives. Run separate instances for separate purposes.

Why AIMFP?

Traditional programming paradigms were designed for humans. AIMFP is optimized for AI-human collaboration:

Challenge	Traditional Approach	AIMFP Solution
Context Loss	AI forgets between sessions	Database-driven persistent state
OOP Complexity	Classes, inheritance, polymorphism	Pure functions, explicit data structures
Infinite Development	Projects never "complete"	Finite completion paths with milestones
Code Reasoning	Parse source code repeatedly	Pre-indexed functions, dependencies, interactions
Inconsistent Standards	Style guides, linters, reviews	Immutable directives enforcing compliance

Core Principles

1. Functional-Procedural Hybrid

python

# ✅ AIMFP-Compliant
def calculate_total(items: List[Item]) -> float:
    """Pure function: deterministic, no side effects"""
    return reduce(lambda acc, item: acc + item.price, items, 0.0)

# ❌ Not AIMFP-Compliant
class Calculator:
    def __init__(self):
        self.total = 0  # Hidden state

    def add_item(self, item):
        self.total += item.price  # Mutation

2. Database-Indexed Logic

Every function, file, and dependency is tracked in SQLite. AI accesses this data through helper tools — not raw SQL:

Code

AI calls: get_functions_by_file(file_id)
→ Returns: all functions in that file with name, purpose, parameters, returns

No source code reparsing required. Instant context retrieval across sessions.

3. AI-Readable Code

Flat structure: No deep inheritance hierarchies
Explicit dependencies: All parameters passed explicitly
Pure functions: Same inputs → same outputs
Metadata annotations: Machine-readable function headers

4. Finite Completion Paths

Code

Project: MatrixCalculator
├── Completion Path (3 stages)
│   ├── 1. Setup (completed)
│   ├── 2. Core Development (in progress)
│   │   ├── Milestone: Matrix Operations
│   │   │   ├── Task: Implement multiply
│   │   │   ├── Task: Implement transpose
│   │   │   └── Task: Add validation
│   │   └── Milestone: Vector Operations
│   └── 3. Finalization (pending)

5. Language-Agnostic

AIMFP works with Python, JavaScript, TypeScript, Rust, Go, and more. FP directives adapt to language-specific syntax while maintaining universal standards.

Architecture Overview

Code

┌─────────────────────────────────────────────────────┐
│            AI Assistant (Claude, GPT-4, etc.)        │
│  - Receives natural language commands                │
│  - Follows directives (FP baseline + project mgmt)   │
│  - Calls MCP tools to read/write databases           │
│  - Generates FP-compliant code                       │
└────────────────────┬────────────────────────────────┘
                     │ MCP Protocol (JSON-RPC over stdio)
┌────────────────────▼────────────────────────────────┐
│                 MCP Server                           │
│  - Exposes helper tools via JSON-RPC                  │
│  - Manages four-database connections                 │
│  - Provides CRUD helpers for all databases           │
│  - No business logic — AI makes all decisions        │
└───┬────────────────────┬─────────────────────────┬──┘
    │                    │                         │
┌───▼──────────────┐ ┌───▼────────────────┐ ┌─────▼─────────────────┐ ┌──────▼────────────────┐
│  aimfp_core.db    │ │  project.db        │ │  user_preferences.db  │ │  user_directives.db   │
│  (Global,        │ │  (Per-Project,     │ │  (Per-Project,        │ │  (Per-Project,        │
│   Read-Only)     │ │   Mutable)         │ │   Mutable)            │ │   Optional)           │
│                  │ │                    │ │                       │ │                       │
│ - FP directives  │ │ - Project metadata │ │ - Directive prefs     │ │ - User directives     │
│ - Project mgmt   │ │ - Files & funcs    │ │ - User settings       │ │ - Execution stats     │
│ - User prefs     │ │ - Task hierarchy   │ │ - AI learning log     │ │ - Dependencies        │
│ - User systems   │ │ - Themes & flows   │ │ - Tracking features   │ │ - Generated code refs │
│ - Helper defs    │ │ - Completion path  │ │ (All opt-in)          │ │ - Source file tracking│
│ - Directive flow │ │ - Runtime notes    │ │                       │ │ (Logs in files)       │
└──────────────────┘ └────────────────────┘ └───────────────────────┘ └───────────────────────┘

Use Case 2 adds a second path that never touches the MCP server. Your automation has to run when no AI session is open, so it imports AIMFP as a plain library instead:

server.ts

┌──────────────────────────────┐        ┌──────────────────────────────┐
│  cron / systemd / your daemon │        │  AI Assistant (a session)     │
│  runs forever; AIMFP does not │        │  present only when you are    │
└───────────────┬──────────────┘        └───────────────┬──────────────┘
                │ starts                                 │ MCP
┌───────────────▼──────────────┐        ┌───────────────▼──────────────┐
│  runner.py  (YOUR project)    │        │         MCP Server            │
│  generated by AIMFP, owned    │        │                               │
│  and editable by you          │        │  check_directive_health       │
│                               │        │  get_directive_execution_stats│
│  import aimfp.hooks  ◄────────┼── a    │  get_recent_directive_errors  │
│  get_due_directives(...)      │  library                              │
│  run_directive(...)           │  call, └───────────────┬──────────────┘
└───────────────┬──────────────┘  not RPC               │ reads
                │ writes                                 │
                └────────────►  user_directives.db  ◄────┘
                                + .aimfp-project/logs/

The runner writes; the AI reads it back later. AIMFP itself is inert in between — it has no timer and starts nothing.

Database Architecture

aimfp_core.db (Global, Read-Only)

Location: Within MCP server installation directory (user-defined location, configured in AI client)

Purpose: Immutable knowledge base containing all AIMFP standards, directives, and helper definitions.

Key Tables:

directives: All FP, project, and user preference directives (workflows, keywords, thresholds)
helper_functions: Database, file, Git, and FP utilities organized across multiple registry files
directive_helpers: Many-to-many junction table mapping directives to their helper functions with execution metadata
categories: Directive groupings (purity, immutability, task management, etc.)
directive_flow: Status-driven directive navigation and routing

Helper-Directive Relationship (New in v1.4):

One directive can use many helpers, one helper can serve many directives
Junction table stores: execution context, sequence order, parameter mappings
Enables flexible helper reuse and clear execution flow
Defined in directive_helpers junction table in aimfp_core.db

Helper Classification:

Tool: All helpers are exposed as MCP tools (AI calls directly via MCP)
Sub-helper (is_sub_helper = TRUE): Internal utility called by other helpers only (not exposed to AI)

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit

1mo ago

Most recent push to the default branch.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Aifp

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "aifp": { "command": "uvx", "args": ["aimfp@latest"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/aifp?style=directory)](https://allmcps.com/mcp/aifp)

HTML Embed

<a href="https://allmcps.com/mcp/aifp"><img src="https://allmcps.com/api/badge/aifp?style=directory" alt="Aifp on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

1/5 checks healthy over the last 46d

37Quality signal: Fair · 37/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity2/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · aimfp@latest (PyPI)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Aifp →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

Aifp

Quick Install

Client Config & Setup

Documentation Overview

AIMFP: AI Modular Functional Procedural Programming

Table of Contents

What is AIMFP?

Two Ways to Use AIMFP

Why AIMFP?

Core Principles

1. Functional-Procedural Hybrid

2. Database-Indexed Logic

3. AI-Readable Code

4. Finite Completion Paths

5. Language-Agnostic

Architecture Overview

Database Architecture

aimfp_core.db (Global, Read-Only)

Related MCP Servers

Adoption & maintenance

Reviews

Frequently Asked Questions about Aifp

AllMCPs Directory Badge

Technical Specs & Signals

Supply-chain signal

Moxie Docs MCP

Own this project?

Share & Embed

Explore more

Aifp

Quick Install

Client Config & Setup

Documentation Overview

AIMFP: AI Modular Functional Procedural Programming

Table of Contents

What is AIMFP?

Two Ways to Use AIMFP

Why AIMFP?

Core Principles

1. Functional-Procedural Hybrid

2. Database-Indexed Logic

3. AI-Readable Code

4. Finite Completion Paths

5. Language-Agnostic

Architecture Overview

Database Architecture

aimfp_core.db (Global, Read-Only)

Related MCP Servers

Adoption & maintenance

Reviews

Frequently Asked Questions about Aifp

AllMCPs Directory Badge

Technical Specs & Signals

Supply-chain signal

Moxie Docs MCP

Own this project?

Share & Embed

Explore more