text stringlengths 0 59.1k |
|---|
Potential enhancements: |
1. **Multi-platform support**: Extend to Facebook, Twitter, LinkedIn ad formats |
2. **A/B testing variations**: Generate multiple versions for testing |
3. **Brand guidelines integration**: Load and apply specific brand rules |
4. **Campaign management**: Track and organize multiple ad campaigns |
5. **Performance analytics**: Integrate with ad platform APIs for metrics |
6. **Template library**: Save successful ad templates for reuse |
7. **Batch processing**: Generate ads for entire product catalogs |
8. **Localization**: Create region-specific ad variations |
9. **Video ad generation**: Extend to Instagram Reels and Stories |
10. **Competitive analysis**: Compare generated ads with competitor campaigns |
11. **Cost optimization**: Estimate and optimize ad spend recommendations |
12. **Approval workflows**: Add review and approval stages before publishing |
<|endoftext|> |
# source: VoltAgent__voltagent/website/examples/mcp-chatgpt.md type: docs |
--- |
id: 6 |
slug: chatgpt-app |
title: ChatGPT App With VoltAgent |
description: Deploy the VoltAgent-based AI agent, expose it over MCP, and connect it to ChatGPT Apps. |
repository: https://github.com/VoltAgent/voltagent/tree/main/examples/with-mcp-server |
--- |
# Building a ChatGPT App With VoltAgent |
This guide shows how to use VoltAgent to deploy an MCP server and connect it to ChatGPT Apps using the Apps SDK. |
Our starting point is the `with-mcp-server` example, which bundles multiple agents, helper tools, and an expense approval workflow behind a Model Context Protocol surface. |
### Setup |
#### Create the app |
Use the VoltAgent CLI to bootstrap the example locally: |
```bash |
pnpm create voltagent-app@latest -- --example with-mcp-server |
cd with-mcp-server |
``` |
The project comes pre-configured with a VoltAgent runtime, the Hono server provider, and an MCP configuration. |
#### Configure the MCP server |
Inside `examples/with-mcp-server/src/index.ts`, an MCPServer instance exposes VoltAgent registries to MCP clients: |
```typescript |
const mcpServer = new MCPServer({ |
name: "voltagent-example", |
version: "0.1.0", |
description: "VoltAgent MCP stdio example", |
protocols: { stdio: true, http: true, sse: true }, |
workflows: { expenseApprovalWorkflow }, |
adapters: { |
prompts: { |
/* prompt registry */ |
}, |
resources: { |
/* read-only knowledge assets */ |
}, |
elicitation: { |
/* human-in-the-loop approvals */ |
}, |
}, |
}); |
``` |
The adapters demonstrate how prompts, resources, and elicitation bridges can be surfaced to MCP clients without modifying the global VoltAgent registry. |
#### Register the MCP server with VoltAgent |
The same file wires agents, workflows, and the MCP server into a single VoltAgent instance: |
```typescript |
new VoltAgent({ |
agents: { |
supervisorAgent, |
translatorAgent, |
storyWriter, |
assistant, |
}, |
mcpServers: { mcpServer }, |
server: honoServer({ port: 3141 }), |
logger, |
}); |
``` |
Key agents include: |
- `AssistantAgent` with helper tools like `current_time` and `confirm_action`. |
- `SupervisorAgent` that delegates to the creative `StoryWriterAgent` or `TranslatorAgent`. |
- Tooling that demonstrates elicitation (manual approval) flows for risky operations. |
#### Add the expense approval workflow |
The example ships with an `Expense Approval Workflow` built via `createWorkflowChain`: |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.