Choosing Your SDK
DRIP/KG-RAG offers two powerful SDKs: Functor SDK for REST API access and MCP SDK for Model Context Protocol integration. This guide helps you choose the right one for your use case.
SDK Comparison
Functor SDK
REST API Client
Direct access to the DRIP/KG-RAG REST API with full control over all operations.
- ✅ Simple REST API interface
- ✅ Full CRUD operations
- ✅ Sync & async support
- ✅ Direct HTTP access
- ✅ Standalone applications
MCP SDK
Model Context Protocol
Agent-first interface for LLM applications with advanced memory management.
- ✅ Agent framework integration
- ✅ Memory-first operations
- ✅ LangChain & CAMEL-AI support
- ✅ Tool-based interface
- ✅ Multi-agent systems
Detailed Comparison
| Feature | Functor SDK | MCP SDK |
|---|---|---|
| Primary Use Case | Direct API access | Agent integration |
| Learning Curve | Low | Medium |
| Memory Operations | Via API endpoints | First-class tools |
| Agent Frameworks | Manual integration | Built-in adapters |
| Async Support | ✅ Full | ✅ Full |
| Type Safety | ✅ Pydantic models | ✅ Pydantic models |
| Best For | Apps, scripts, services | AI agents, chatbots |
When to Use Functor SDK
✅ Choose Functor SDK if you:
- Building traditional applications: Web apps, mobile backends, data pipelines
- Need full API control: Direct access to all REST endpoints
- Want simplicity: Straightforward request/response patterns
- Have existing REST integrations: Easy to add to current architecture
- Building standalone services: Microservices, batch processors
- Prefer HTTP semantics: Familiar REST patterns
Code Example
When to Use MCP SDK
✅ Choose MCP SDK if you:
- Building AI agents: LangChain, CAMEL-AI, or custom agent systems
- Need memory management: Episodic, semantic, and procedural memory
- Want tool-based interfaces: MCP tools for agent frameworks
- Building multi-agent systems: Coordinated agent interactions
- Need advanced memory features: Memory consolidation, retrieval strategies
- Prefer declarative patterns: Tool definitions and prompts
Code Example
Use Case Examples
Scenario 1: Data Processing Pipeline
Recommendation: Functor SDK
A batch processing system that ingests documents, processes them, and indexes into knowledge graphs. Needs direct control over API operations with error handling.
Scenario 2: Intelligent Chatbot
Recommendation: MCP SDK
A conversational AI that remembers past interactions, retrieves relevant knowledge, and maintains user context across sessions. Needs episodic memory and semantic retrieval.
Scenario 3: Research Assistant
Recommendation: Both
Use Functor SDK for document ingestion and management. Use MCP SDK for the AI assistant that helps users explore and query the research database.
Scenario 4: Analytics Dashboard
Recommendation: Functor SDK
A web dashboard showing knowledge graph statistics, source management, and system health. Needs direct access to all API endpoints with minimal abstraction.
Using Both SDKs Together
You can use both SDKs in the same application for different purposes:
Migration Between SDKs
From Functor SDK to MCP SDK
From MCP SDK to Functor SDK
Quick Decision Tree
Choose Your SDK:
→ Yes? Use MCP SDK
→ No? Continue to #2
→ Yes? Use MCP SDK
→ No? Continue to #3
→ Yes? Use MCP SDK
→ No? Continue to #4
→ Yes? Use Functor SDK
→ Not sure? Use Functor SDK (easier to start)