Tidymodels MCP Server

Created By
JavOrracaa year ago
This MCP server was developed to improve Cline's agentic workflows by being up-to-date with the public repositories and docs under
Overview

what is Tidymodels MCP Server?

Tidymodels MCP Server is a server developed to enhance Cline's coding workflows by making them context-aware of all public repositories and documentation related to Tidymodels.

how to use Tidymodels MCP Server?

To use the Tidymodels MCP Server, developers can integrate it into their Cline workflows, allowing for improved context awareness when accessing public repositories and documentation.

key features of Tidymodels MCP Server?

  • Context-aware coding workflows for Cline's agentic AI.
  • Integration with public repositories and documentation.
  • Supports the Model Context Protocol (MCP) for enhanced functionality.

use cases of Tidymodels MCP Server?

  1. Enhancing AI-driven coding assistance by providing relevant context.
  2. Streamlining access to documentation and resources for developers.
  3. Facilitating collaborative coding efforts by improving context awareness.

FAQ from Tidymodels MCP Server?

  • What is the purpose of the Tidymodels MCP Server?

The Tidymodels MCP Server aims to improve coding workflows by making them context-aware of relevant public resources.

  • Is the Tidymodels MCP Server free to use?

Yes! The server is open-source and available for public use.

  • How can I contribute to the Tidymodels MCP Server?

Contributions are welcome! You can submit issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JavOrraca
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago