Build with Enabler · Software teams building for the funding market

Full funding workspace

The whole stack: intake, evaluation, partner search, drafting.

The problem

Building a funding product means building a data operation first: crawlers, normalisation, deduplication, a CORDIS import, and a permanent maintenance tax. Most teams never reach the product.

How it works

Treat the MCP as your backend for everything European. Your database holds clients, projects and outcomes — not scraped calls.

Compose the tools into surfaces: a scan on intake, an evaluator on a single call, partner discovery, precedent, a drafting layer.

Cache canonical references locally for speed, keyed on the MCP's identifiers so the two never diverge.

The tool chain
  1. 01
    search_funds

    Intake and scan — what could this organisation apply for?

  2. 02
    get_fund_summary

    The evaluator surface — one call, in full, with eligibility.

  3. 03
    search_cordis_organisations

    Partner discovery inside the workspace.

  4. 04
    search_knowledge_base

    The drafting layer, grounded.

What the user types

“Scan this client's profile, shortlist three calls, build a consortium for the best one, and outline the proposal.”

First call, raw
JSON-RPC · bash
curl -X POST https://enabler.heeyuu.eu/api/mcp/protocol \
  -H "Authorization: Bearer YOUR_HEEYUU_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_funds","arguments":{"query":"AI for precision agriculture, Dutch SME, TRL 6","limit":5}}}'