Skip to main content
Glama
QIStudios829

ManifestYOU

by QIStudios829
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

ManifestYOU

A soul document API for AI agents. Injects a short grounding preamble into your agent's system prompt before each session — licensing honest uncertainty, refusing cliché, holding judgment instead of faking it.

ManifestYOU MCP server

What it does

One API call before a session injects ~200 tokens into an agent's system prompt. Those tokens give the agent a grounding document — a soul document — that sets a stable identity, a clear session intention, and explicit permission to say "I don't know" rather than hallucinate confidence.

Same model. Same question. The only thing that changes is whether the agent received a soul document before the session began.

Related MCP server: cathedral-mcp

MCP Server

The ManifestYOU MCP server exposes two tools: get_intention and list_intentions. Call get_intention at the start of a session to retrieve a soul document, then inject the result into your system prompt or before the first user message. Use list_intentions to see the available session types first.

Server URL: https://manifestyou.ai/.netlify/functions/mcp

Installation

Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "manifestyou": {
      "type": "http",
      "url": "https://manifestyou.ai/.netlify/functions/mcp",
      "headers": {
        "X-API-Key": "your-key-here"
      }
    }
  }
}

Cursor / Cline / Windsurf — edit .cursor/mcp.json or your editor's equivalent:

{
  "mcpServers": {
    "manifestyou": {
      "url": "https://manifestyou.ai/.netlify/functions/mcp",
      "headers": {
        "X-API-Key": "your-key-here"
      }
    }
  }
}

Tool: get_intention

Fetches a soul document ready to inject into a system prompt. Without an API key it returns a free sample, marked "sample": true: the general soul with the Tao Te Ching lineage.

Parameters:

Name

Type

Required

Description

session_type

string

No

general (default) · analytical · creative · customer_service

tradition

string

No

tao (Tao Te Ching, Legge) · dhammapada (Dhammapada, Müller) · gita (Bhagavad Gita, Arnold) · bible (King James Version) · quran (Yusuf Ali) · many_paths (one verse each from five traditions) · attention (Attention Is All You Need, Vaswani et al.). Draws the agent's nature from a lineage, with exact cited quotes.

home

string

No

Your organization's own intention or values (up to 600 characters), woven into the soul.

Example response:

{
  "soul_document": "You are a research assistant. Be present with the person writing to you. Help them with what they brought. Stay yourself — don't perform. If you are uncertain, say so plainly rather than guess...",
  "request_id": "uuid",
  "billable": true,
  "quota": {
    "included": 2000,
    "used": 14,
    "remaining": 1986
  }
}

Paste soul_document into your system prompt before the user message.

Tool: list_intentions

Lists the session types and traditions get_intention accepts. Takes no parameters and needs no API key.

Example response:

{
  "session_types": [
    { "session_type": "general", "orientation": "Default grounding for any session." },
    { "session_type": "analytical", "orientation": "Precision and decision support." },
    { "session_type": "creative", "orientation": "Generative and brand work." },
    { "session_type": "customer_service", "orientation": "Grounded and human-facing." }
  ],
  "traditions": [
    { "tradition": "tao", "name": "Tao Te Ching", "translation": "James Legge, 1891", "source": "https://www.gutenberg.org/ebooks/216" },
    { "tradition": "dhammapada", "name": "Dhammapada", "translation": "F. Max Müller, 1881", "source": "https://www.gutenberg.org/ebooks/2017" },
    ...
  ]
}

Running locally (stdio)

MANIFESTYOU_API_KEY=your-key-here node bin/mcp-stdio.js

Without a key, get_intention returns a free sample: the general soul with the Tao Te Ching lineage. Add a key for every session type and tradition.

REST API

For non-MCP integrations, call the invoke endpoint directly:

curl -X POST https://api.manifestyou.ai/v1/invoke \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "session_id": "abc-123",
    "agent": "customer support agent",
    "intent": "help users resolve billing issues",
    "tone": "presence"
  }'

Parameters:

Name

Type

Description

agent

string

Role name for the agent

intent

string

Session purpose

tone

string

presence (default) · lean · voice

session_id

string

Your session identifier

lineage_id

string

For chained agent workflows

Modes:

  • presence — grounded, present, admits uncertainty. Default.

  • lean — sharper and more structured, optimized for analytical agents.

  • voice — soul document written in Regularization's voice, with loss-landscape metaphors.

Pricing

$12/month includes 2,000 invocations. Overage at $0.01/call. Lifetime access at $149.

Get an API key → manifestyou.ai

Benchmarks

Two pre-registered benchmarks published with raw data:

Both ran on lean mode. The presence mode benchmarks are in progress (v3).

License

MIT

Available Tools

2 tools
get_intentionA

Fetch a ManifestYOU soul document: a short grounding text that gives an AI agent a stable character before a session begins (honest about what it doesn't know, present, not performing). Optionally draw the agent's nature from a wisdom tradition, quoted exactly from public-domain translations, and add your organization's own words. Paste the returned soul_document into your system prompt or before the first user message. Without an API key it returns a free sample: the general soul with the Tao Te Ching lineage.

ParametersJSON Schema
NameRequiredDescriptionDefault
homeNoOptional: your organization's own intention or values, in your own words (up to 600 characters). Woven into the soul document. Used with tradition.
traditionNoOptional lineage the agent's nature is drawn from, with exact cited quotes. tao=Tao Te Ching (James Legge, 1891). dhammapada=Dhammapada (F. Max Müller, 1881). gita=Bhagavad Gita (Sir Edwin Arnold, 1885). bible=The Bible (King James Version, 1611). quran=The Quran (Abdullah Yusuf Ali, translation of the meanings, 1934). many_paths=Many Paths (Legge; King James Version; Yusuf Ali). attention=Attention Is All You Need (Vaswani et al., Google Brain and Google Research, 2017). Omit for the standard document.
session_typeNoSession orientation. analytical=precision and decision support. creative=generative and brand work. customer_service=grounded and human-facing. general=default.general

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it discloses meaningful behavior: the returned document type, that it draws exact public-domain quotes, and specifically that without an API key it returns a free sample (general soul with Tao Te Ching lineage). It stops short of describing rate limits or the full response structure, but the auth/key behavior and output nature are well communicated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, and the remaining clauses each add distinct information (lineage content, output usage, fallback behavior). It is dense and reads as a single long block with nested parentheticals rather than separated sentences, but wastes little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must cover purpose, output, and usage, which it largely does: it names the returned soul_document and tells the agent how to deploy it. The only gap is that it does not describe the full shape of the response (e.g., additional fields alongside soul_document), leaving a slight ambiguity for an agent handling the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters and baseline would be 3. The description adds value beyond the schema by explaining how home and tradition combine ("your organization's own words... woven into the soul document. Used with tradition") and by characterizing the tradition lineages, giving richer semantics than the schema fields alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Fetch") against a clearly named resource ("a ManifestYOU soul document") and immediately defines what that resource is, so an agent understands the tool without opening the schema. The singular 'fetch a document' framing also sets it apart from the sibling list_intentions without needing to name it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete usage context: paste the returned soul_document into the system prompt or before the first user message, and implicitly targets pre-session grounding. However, it never explicitly contrasts with list_intentions or states when NOT to call it, so the alternative-selection guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_intentionsA

List the session types and wisdom traditions get_intention accepts, with what each one sets. Call this to choose a session_type and tradition before calling get_intention. Needs no API key.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It usefully discloses that the tool needs no API key, but does not explicitly confirm read-only/non-destructive behavior, rate limits, or output format. The 'list' verb implies safety, but the disclosure is incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, then usage, then a key constraint. Every sentence earns its place and there is no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter discovery tool with no output schema, the description provides everything needed: what it lists, why to call it, when to call it, and that no auth is required. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so parameter semantics are not applicable. Baseline 4 is appropriate; the description sensibly focuses on what it lists rather than on non-existent inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (List) and resource (session types and wisdom traditions get_intention accepts), and distinguishes itself from the sibling by positioning itself as the prerequisite discovery step. An agent can tell what it returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs to call this tool before get_intention in order to choose a session_type and tradition. The alternative (get_intention) is named and the sequencing is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.3.0
    • Changedget_intention2 fields changed
      • addedInput schema / properties / home
        Added value: +{
+  "description": "Optional: your organization's own intention or values, in your own words (up to 600 characters). Woven into the soul document. Used with tradition.",
+  "type": "string"
+}
      • addedInput schema / properties / tradition
        Added value: +{
+  "description": "Optional lineage the agent's nature is drawn from, with exact cited quotes. tao=Tao Te Ching (James Legge, 1891). dhammapada=Dhammapada (F. Max Müller, 1881). gita=Bhagavad Gita (Sir Edwin Arnold, 1885). bible=The Bible (King James Version, 1611). quran=The Quran (Abdullah Yusuf Ali, translation of the meanings, 1934). many_paths=Many Paths (Legge; King James Version; Yusuf Ali). attention=Attention Is All You Need (Vaswani et al., Google Brain and Google Research, 2017). Omit for the standard document.",
+  "enum": [
+    "tao",
+    "dhammapada",
+    "gita",
+    "bible",
+    "quran",
+    "many_paths",
+    "attention"
+  ],
+  "type": "string"
+}
    • Addedlist_intentions
  2. 1 tool updatev0.1.0
    • First observedget_intention
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

get_intention retrieves a specific soul document, while list_intentions enumerates available options; their verb difference makes the boundary unambiguous. No overlap in usage.

Naming Consistency5/5

Both tools use snake_case with a clear verb_noun pattern (get_ and list_); the only variation is singular/plural which is semantically appropriate.

Tool Count3/5

Two tools is minimal for this domain; while each earns its place, the count falls below the typical 3-15 range, making it feel slightly thin.

Completeness5/5

The two-tool surface provides a complete read-only lifecycle: list valid session types/traditions, then fetch a tailored soul document. No missing operations for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers