Skip to main content
ClaudeWave
angelus213 avatar
angelus213

foundry-api-workflows

View on GitHub

Verified n8n workflows, Pipedream actions and remote MCP tools for Foundry/API.

MCP ServersOfficial Registry0 stars0 forksJavaScriptMITUpdated today
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/angelus213/foundry-api-workflows
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "foundry-api-workflows": {
      "command": "node",
      "args": ["/path/to/foundry-api-workflows/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/angelus213/foundry-api-workflows and follow its README for install instructions.
Use cases

MCP Servers overview

# Foundry/API workflow and MCP starter kit

A public, credential-free starter kit for turning the nine [Foundry/API](https://prodapi.live) products into importable automations and bounded agent tools. The repository contains three n8n workflow templates, nine Pipedream registry-style actions, a restricted local MCP wrapper and a registry-ready remote MCP endpoint.

## Start here

| Outcome | Asset | Products |
|---|---|---|
| Build a local-market prospecting workflow | `n8n/local-sales-intelligence.json` | Google Maps Lead Extractor, B2B Domain Enricher, Review Sentiment Analyzer |
| Turn documents and text into validated data | `n8n/document-automation.json` | DocuStruct, JSON-Forge |
| Prepare public web content for retrieval | `n8n/rag-content-ingestion.json` | RenderCloud, RAG-Feeder |
| Give an MCP client bounded API tools | `https://prodapi.live/mcp` or `mcp/` | Seven transformation, discovery and analysis tools |

## Product action index

| Action | REST endpoint | Pipedream source |
|---|---|---|
| Render Web Page | `/api/v1/rendercloud/render` | `pipedream/actions/render-web-page` |
| Create Auth Sandbox Session | `/api/v1/auth-scraper/sessions` | `pipedream/actions/create-auth-sandbox-session` |
| Forge Structured JSON | `/api/v1/json-forge/forge` | `pipedream/actions/forge-structured-json` |
| Extract Document | `/api/v1/docustruct/extract` | `pipedream/actions/extract-document` |
| Prepare RAG Content | `/api/v1/rag-feeder/convert` | `pipedream/actions/prepare-rag-content` |
| Create Change Monitor | `/api/v1/trackpulse/monitors` | `pipedream/actions/create-change-monitor` |
| Enrich B2B Domain | `/api/v1/b2b-domain-enricher/enrich` | `pipedream/actions/enrich-domain` |
| Search Local Businesses | `/api/v1/google-maps-lead-extractor/search` | `pipedream/actions/search-local-businesses` |
| Analyze Public Reviews | `/api/v1/review-sentiment-analyzer/analyze` | `pipedream/actions/analyze-reviews` |

## Credentials and safety

No credential, token, review, customer data or test secret is committed. Set the API key in n8n Header Auth, a Pipedream connected app, the MCP remote `X-API-Key` header or the local `FOUNDRY_API_KEY` environment variable. Use only sources and systems you are authorized to process. Auth-Scraper remains a public demo sandbox; TrackPulse monitoring must be configured only for authorized URLs and webhook destinations.

## Verification

Run `npm test` from the repository root. The validator parses every workflow, checks Pipedream and MCP syntax, verifies remote registry metadata, scans for credential-like values and runs the MCP client tests without calling production APIs.

## Links

[Product site](https://prodapi.live) · [Developer Hub](https://prodapi.live/developers) · [API access](https://prodapi.live/account/api-access) · [MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.angelus213/foundry-api) · [Security](https://prodapi.live/security) · [Support](https://prodapi.live/support) · [Pipedream request](https://github.com/PipedreamHQ/pipedream/issues/21441)
apideveloper-toolsmcpn8npipedreamworkflow-automation

What people ask about foundry-api-workflows

What is angelus213/foundry-api-workflows?

+

angelus213/foundry-api-workflows is mcp servers for the Claude AI ecosystem. Verified n8n workflows, Pipedream actions and remote MCP tools for Foundry/API. It has 0 GitHub stars and was last updated today.

How do I install foundry-api-workflows?

+

You can install foundry-api-workflows by cloning the repository (https://github.com/angelus213/foundry-api-workflows) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is angelus213/foundry-api-workflows safe to use?

+

angelus213/foundry-api-workflows has not been audited yet by our security agent. Review the original repository on GitHub before using it in production.

Who maintains angelus213/foundry-api-workflows?

+

angelus213/foundry-api-workflows is maintained by angelus213. The last recorded GitHub activity is from today, with 1 open issues.

Are there alternatives to foundry-api-workflows?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy foundry-api-workflows to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: angelus213/foundry-api-workflows
[![Featured on ClaudeWave](https://claudewave.com/api/badge/angelus213-foundry-api-workflows)](https://claudewave.com/repo/angelus213-foundry-api-workflows)
<a href="https://claudewave.com/repo/angelus213-foundry-api-workflows"><img src="https://claudewave.com/api/badge/angelus213-foundry-api-workflows" alt="Featured on ClaudeWave: angelus213/foundry-api-workflows" width="320" height="64" /></a>

More MCP Servers

foundry-api-workflows alternatives