docs: Add VoltAgent framework integration documentation

[omeraplak]

Sweep Summary

Adds documentation for integrating Composio with VoltAgent framework, enabling VoltAgent agents to connect with external tools and services.

• Created voltagent.mdx with step-by-step instructions for setting up and configuring VoltAgent with Composio.
• Added practical example showing how to use MCPConfiguration to enable a VoltAgent agent to star GitHub repositories.
• Updated navigation in docs.yml to include the new VoltAgent documentation page under the frameworks section.

---

Ask Sweep AI questions about this PR

This PR adds documentation for integrating Composio with VoltAgent agents, allowing them to connect with external tools and services.

The documentation includes step-by-step instructions on how to configure and use Composio with VoltAgent, with a practical example showing how to star GitHub repositories.

• Added voltagent.mdx to the frameworks section

Includes complete setup instructions and working code examples
Demonstrates how to use MCPConfiguration with VoltAgent"

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
composio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 12, 2025 4:51pm

[entelligence-ai-pr-reviews]

Review Summary

Skipped posting 1 drafted comments based on your review threshold. Feel free to update them here.

Draft Comments

fern/frameworks/voltagent.mdx:44-50

The `MCPConfiguration` is defined twice with different syntax. In the first example it's created with `new MCPConfiguration()` but in the execution example it's created with `new MCP()` which is inconsistent.

Scores:

• Production Impact: 2
• Fix Specificity: 5
• Urgency Impact: 2
• Total Score: 9

Reason for filtering: The comment identifies an inconsistency in API usage (MCPConfiguration vs MCP) but doesn't demonstrate a high production impact. The fix is straightforward but the issue is more of a documentation/consistency problem than a critical bug.

Analysis: The inconsistency in documentation is unlikely to cause production failures as it's just showing different ways to initialize the configuration. The fix is very specific and clear, but the urgency is low since this is a documentation consistency issue. With a total score of 9, which is below the threshold of 13, this comment should be removed.