AppFactory

Overview Schema Source Related Servers Discussions Admin

App Inject Config

app_inject_config

Idempotent

Fill a scaffolded app's AppConfig and StoreKit tokens with Supabase, proxy, PostHog, product IDs, credits, and paywall strategy after backend and RevenueCat values exist.

Instructions

Fill in the scaffolded app's AppConfig and StoreKit tokens (Supabase, proxy, PostHog, product ids, credits, paywall strategy).

Use when: after backend and RevenueCat values exist. Credit fields default to 15/10/10/30/60 and pack amounts must match the server-side PACK_MAP. Not for: spec-driven changes (edit app.spec.json, then app_sync_spec). Returns: {ok, changed: [files]}.

Input Schema

Name	Required	Description
`posthog_key`	No	PostHog project API key.
`privacy_url`	No	Public privacy policy URL.
`project_dir`	Yes	Path to the scaffolded app project directory.
`ai_proxy_url`	No	URL of the deployed AI proxy/edge function.
`supabase_url`	No	Supabase project URL, e.g. https://abcd.supabase.co.
`support_email`	No	Public support email address.
`product_weekly`	No	Weekly subscription product id.
`product_yearly`	No	Yearly subscription product id.
`revenuecat_key`	No	RevenueCat public SDK key (appl_...).
`weekly_credits`	No	Credits granted per week on the weekly plan (default 10).
`yearly_credits`	No	Credits granted per month on the yearly plan (default 15).
`paywall_strategy`	No	'hard_only' (hard paywall only) or 'hard_and_offer' (default: plus a discounted offer paywall on dismiss).
`credit_pack_large`	No	Credits in the large top-up pack (default 60).
`credit_pack_small`	No	Credits in the small top-up pack (default 10).
`supabase_anon_key`	No	Supabase anon (public) key.
`credit_pack_medium`	No	Credits in the medium top-up pack (default 30).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv0.1.5Oct 1, 2026
- addedInput schema / properties / ai_proxy_url / description
```
Added value: +"URL of the deployed AI proxy/edge function."
```
- addedInput schema / properties / credit_pack_large / description
```
Added value: +"Credits in the large top-up pack (default 60)."
```
- addedInput schema / properties / credit_pack_medium / description
```
Added value: +"Credits in the medium top-up pack (default 30)."
```
- addedInput schema / properties / credit_pack_small / description
```
Added value: +"Credits in the small top-up pack (default 10)."
```
- addedInput schema / properties / paywall_strategy / description
```
Added value: +"'hard_only' (hard paywall only) or 'hard_and_offer' (default: plus a discounted offer paywall on dismiss)."
```
- addedInput schema / properties / posthog_key / description
```
Added value: +"PostHog project API key."
```
- addedInput schema / properties / privacy_url / description
```
Added value: +"Public privacy policy URL."
```
- addedInput schema / properties / product_weekly / description
```
Added value: +"Weekly subscription product id."
```
- addedInput schema / properties / product_yearly / description
```
Added value: +"Yearly subscription product id."
```
- addedInput schema / properties / project_dir / description
```
Added value: +"Path to the scaffolded app project directory."
```
- addedInput schema / properties / revenuecat_key / description
```
Added value: +"RevenueCat public SDK key (appl_...)."
```
- addedInput schema / properties / supabase_anon_key / description
```
Added value: +"Supabase anon (public) key."
```
- addedInput schema / properties / supabase_url / description
```
Added value: +"Supabase project URL, e.g. https://abcd.supabase.co."
```
- addedInput schema / properties / support_email / description
```
Added value: +"Public support email address."
```
- addedInput schema / properties / weekly_credits / description
```
Added value: +"Credits granted per week on the weekly plan (default 10)."
```
- addedInput schema / properties / yearly_credits / description
```
Added value: +"Credits granted per month on the yearly plan (default 15)."
```
First observedv0.1.1Sep 29, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive, closed-world). The description adds genuinely new constraints: credit-field defaults and the requirement that pack amounts match the server-side PACK_MAP. Missing auth/permission context, but the added constraint is meaningful.

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?

Front-loaded purpose sentence followed by clearly labeled 'Use when', 'Not for', and 'Returns' segments. No filler; every clause carries actionable information.

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 16-parameter write tool with full schema coverage and an output schema, the description covers purpose, preconditions, alternatives, key defaults, and the PACK_MAP constraint. Nothing material 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?

Schema coverage is 100%, so per-field semantics are already documented (baseline 3). The description adds value by summarizing the credit defaults and flagging the cross-parameter PACK_MAP consistency requirement, which the schema cannot express.

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?

Uses a specific verb ('Fill in') against a named resource ('scaffolded app's AppConfig and StoreKit tokens') and enumerates the exact token categories covered. An agent can distinguish it from siblings like app_sync_spec 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?

Explicit 'Use when: after backend and RevenueCat values exist' gives the precondition, and 'Not for: spec-driven changes (edit app.spec.json, then app_sync_spec)' names both the exclusion and the correct alternative. This is the gold standard for routing.

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

Deploy Server