Skip to main content

Resources Overview

Resources are a powerful feature of MCP (Model Context Protocol) that allow you to provide context and data to AI models. Resources enable servers to expose files, database schemas, application-specific information, and more to clients.

What are Resources?​

Resources in Reeva allow you to:

  • Provide static or dynamic context to AI models
  • Share configuration files, documentation, and reference data
  • Expose database schemas and application state
  • Connect external data sources like Notion pages
  • Scrape and summarize web content from any URL

Resource Types​

Reeva supports four types of resources:

Text Resources​

Text resources store plain text, markdown, JSON, or any text-based content directly in Reeva. They're perfect for:

  • Configuration files
  • Documentation snippets
  • Code examples
  • Instructions or guidelines

File Resources​

File resources allow you to upload and store files of any type:

  • PDFs and documents
  • Images
  • Data files (CSV, JSON, etc.)
  • Any binary file up to 25MB

Notion Resources​

Notion resources connect to your Notion workspace to expose:

  • Notion pages
  • Notion databases

This allows AI models to access your documentation, knowledge bases, and project information stored in Notion.

Website Resources​

Website resources allow you to save a URL and configure how its content is delivered:

  • URL Only: Just returns the URL
  • Live Markdown: Scrapes fresh content on each read
  • Cached Markdown: Scrapes once at creation
  • Live Summary: AI summary on each read
  • Cached Summary: AI summary at creation

This is perfect for documentation sites, news sources, or any web content you want to provide as context to AI models.

Credits​

Some resources can incur credits when they fetch/scrape content or generate summaries (for example, Website Resources using Live/Cached Markdown or Live/Cached Summary). See Website Resources and Credits for details.

How Resources Work​

  1. Create: Define a resource with a name, type, and content
  2. Link: Attach the resource to one or more MCP servers
  3. Access: AI clients connected to those servers can read the resource

Resources are identified by URIs that must be unique within each server they are linked to. The same URI can exist across different servers, but a server cannot have two resources with the same URI.

Key Features​

  • Flexible Storage: Small text stored inline, large files in cloud storage
  • Server Linking: One resource can be shared across multiple servers
  • Search and Filter: Easily find resources by name, type, or description
  • Version Control: Track when resources were created and updated
  • Access Control: Resources are private to your account

Common Use Cases​

  • Context Injection: Provide coding standards, style guides, or project documentation
  • Configuration Management: Share API specifications, environment details
  • Knowledge Base: Connect Notion documentation for Q&A
  • Reference Data: Store product catalogs, pricing tables, lookup data
  • Examples and Templates: Provide code examples or document templates
  • Web Content: Scrape and summarize documentation sites, news, or any web page

Getting Started​

  1. Navigate to the Resources section in the left sidebar
  2. Click + New Resource to create your first resource
  3. Choose a resource type (Text, File, Notion, or Website)
  4. Fill in the details and content
  5. Link the resource to your servers

For detailed guides on each resource type, see: