Ollama Pydantic Project

Created By
jageenshuklaa year ago
Created sample project for pydantic agent with local ollama model with mcp server integration.
Overview

What is the Ollama Pydantic Project?

The Ollama Pydantic Project is a sample project that demonstrates how to integrate a local Ollama model with the Pydantic agent framework, enabling the creation of an intelligent chatbot agent connected to an MCP server.

How to use the Ollama Pydantic Project?

To use the project, clone the repository, set up a virtual environment, install the required dependencies, ensure the Ollama server is running, and then run the Streamlit application to interact with the chatbot.

Key features of the Ollama Pydantic Project?

  • Local Ollama model integration for generating responses.
  • Pydantic framework for data validation and interaction.
  • Connection to an MCP server for enhanced agent capabilities.
  • User-friendly chatbot interface built with Streamlit.

Use cases of the Ollama Pydantic Project?

  1. Creating intelligent chatbots for customer support.
  2. Developing interactive applications that require natural language processing.
  3. Building tools that utilize machine learning models for data-driven responses.

FAQ from the Ollama Pydantic Project?

  • What is required to run the project?

You need Python 3.8 or higher, a local Ollama server, and an MCP server set up.

  • Is there a user interface?

Yes, the project provides a Streamlit-based user interface for interacting with the chatbot.

  • Can I contribute to the project?

Yes, contributions are welcome! You can open issues or submit pull requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jageenshukla
Star
0
Language
Python
License
-

Recommend Servers

View All
Valuein MCP Server - US SEC Financial Data
@valuein

Institutional-grade SEC financial data for AI agents — in one line of config. Connect Claude, Cursor, ChatGPT, Codex, or any MCP-compatible client to 35 years of SEC EDGAR data (1990–today, 16,000+ US companies, 100M+ financial facts) and let your agent do the analysis. MCP Server URL: https://mcp.valuein.biz/mcp What your agent can do Look up any US public company — tickers, CIKs, sectors, S&P 500 membership Pull fundamentals — income statement, balance sheet, cash flow, annual or quarterly Read financial ratios — margins, ROIC, leverage, turnover, cash conversion Compare to peers — automated peer selection + side-by-side ratios Link straight to the source filing — 10-K, 10-Q, 8-K URLs from SEC EDGAR Audit capital allocation — buybacks, dividends, capex, M&A history Screen the market — factor screens, earnings signals, quality filters Run point-in-time backtests — survivorship-free historical universes, no look-ahead bias Verify every number — trace any fact back to the exact filing and line item Search filing text — semantic search across Risk Factors, MD&A, and footnotes Stream bulk data — signed R2 URLs for DuckDB / Pandas workflows (Pro+) 15 tools + 8 built-in analyst/quant/PM playbooks ("Margin & Moat Teardown", "Peer Benchmarking Memo", "Survivorship-Free Backtest", and more). Built for Analysts & PMs running earnings reviews, forensic tear-downs, and peer benchmarking without leaving their AI assistant Quants building PIT factor models and survivorship-free backtests Developers shipping agentic financial products without licensing a data vendor Financial content creators pulling live SEC data into research workflows One token. Every distribution channel. The same Bearer unlocks the Python SDK, Excel Power Query, REST API, and this MCP server. Subscribe once, use everywhere. For more information visit our documentation: https://valuein.biz/mcp

a day ago
Lattis

a day ago
Tickstem
@tickstem

12 hours ago
Toflow.ai

6 hours ago
Kamy
@Kamy Dev

17 hours ago
Memtrace
@syncable-dev

Memtrace — Structural Memory for AI Coding Agents The Problem Every AI coding agent — Claude Code, Cursor, Codex, Copilot — starts each turn completely blank. It re-reads raw source files and re-derives the full call graph, type hierarchy, and import tree from scratch on every single invocation. That structural rework burns 60–90% of the context window before any real reasoning begins. Less than 5% of tokens in a typical agentic coding session contribute genuine new intelligence. The rest is expensive, redundant noise — and it compounds: accuracy drops 40% as sessions grow, stale context crowds out signal, and summaries strip out the structural relationships agents need most. The Solution Memtrace is a bi-temporal structural memory layer that turns your codebase into a live, queryable knowledge graph — compiled from the AST, not guessed from embeddings. Every function, class, interface, and API endpoint becomes a typed node with deterministic relationships. Every file save becomes a queryable episode with timestamps, so agents can reason about structure, detect regressions, and time-travel through their own work without re-reading anything. One Rust binary. Zero configuration. Five-minute install. What agents can do with it Find callers, callees, and dependencies instantly — no file scanning, no token waste Compute blast radius before making a change — know exactly what breaks before anything is touched Detect structural drift between sessions — catch regressions the moment they happen, not at PR review Time-travel through code evolution — query any prior state of any symbol, not just git commits Search across the full codebase with hybrid retrieval — BM25 full-text + HNSW vector + graph traversal fused in one query Map API topology across services — cross-repo HTTP call graphs, dependency chains, dead endpoint detection Benefits −90% token cost on structural queries (Mem0) +26% accuracy on multi-step agentic tasks (Mem0) −91% p95 latency on structural lookups vs. RAG baselines +32.8% SWE-bench bug-fix success rate when agents have graph context (RepoGraph) 200–800ms per-save re-indexing — every file save is a queryable episode in under a second 40+ MCP tools covering indexing, search, relationships, impact analysis, temporal evolution, API topology, graph algorithms, and direct Cypher queries 12 languages + 3 IaC formats supported via Tree-sitter grammars Local-first, closed-source Rust — code never leaves the machine, no account required, no telemetry

a day ago
Socialcrawl Mcp
@Ridio

`socialcrawl-mcp` is an MCP server that connects AI agents to the [SocialCrawl API](https://socialcrawl.dev) — a unified social media data API covering 21 platforms and 108 endpoints. Retrieve profiles, posts, comments, search results, trending content, and analytics from TikTok, Instagram, YouTube, Twitter/X, LinkedIn, Reddit, and 15 more platforms. One API key, one consistent response format, every platform. **What the MCP server does:** - Discovers available platforms and endpoints dynamically - Fetches live social media data on your behalf - Validates requests locally before making API calls (saves credits) - Provides built-in API documentation the agent can query on demand ## Installation ### Claude Code (quickest) ```bash claude mcp add --scope user socialcrawl -- npx -y socialcrawl-mcp ``` Then set your API key: ```bash claude mcp add-env socialcrawl SOCIALCRAWL_API_KEY sc_your_key_here ``` ### Claude Desktop Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows): ## Setup ### 1. Get your API key Sign up at [socialcrawl.dev](https://socialcrawl.dev) and grab your API key from the dashboard. Every account starts with **100 free credits** — no credit card required. ### 2. Add the key to your config Replace `sc_your_key_here` in the installation config above with your actual API key (starts with `sc_`). > [!TIP] > You can also set `SOCIALCRAWL_API_KEY` as a system environment variable instead of putting it in the MCP config. The discovery and documentation tools work even without a key — only actual API requests need one. ## Usage Ask your AI agent in natural language. The MCP server handles the rest.

2 days ago