Vinkius
Upstream Lens

Upstream Lens MCP for AI. Query Geospatial Data from Natural Language

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Upstream Lens MCP on Cursor AI Code EditorUpstream Lens MCP on Claude Desktop AppUpstream Lens MCP on OpenAI Agents SDKUpstream Lens MCP on Visual Studio CodeUpstream Lens MCP on GitHub Copilot AI AgentUpstream Lens MCP on Google Gemini AIUpstream Lens MCP on Lovable AI DevelopmentUpstream Lens MCP on Mistral AI AgentsUpstream Lens MCP on Amazon AWS Bedrock

Connect to your AI in seconds.

Upstream Lens monitors environmental assets and conservation projects using satellite imagery and field data. It lets your AI client analyze geospatial metadata, track changes over time, and pull project notes directly from a natural conversation.

You can list all active projects, query available imagery layers (Sentinel, Landsat), and verify property details without leaving the chat window.

What your AI can do

Get property details

Fetches specific, detailed records for a known property feature ID.

Get organization info

Retrieves core metadata about your entire organization within Upstream Lens.

Check api health

Confirms if the Upstream Lens API is currently active and connected.

+ 5 more capabilities included
Discover all active projects

Lists every environmental project or portfolio managed under the Upstream Lens account.

Analyze property imagery layers

Retrieves metadata about available satellite images (e.g., true color, NDVI) for a specific geographic area.

Track historical field data

Pulls project notes and detailed observations to build an auditable timeline of changes at a site.

Get organization status

Retrieves the metadata for your connected Upstream Lens account or verifies API health.

Included with Plan

Waiting for input…

AI Agent

Upstream Lens MCP Server: 8 Tools for Environmental Data

Use these eight tools to run deep queries on environmental assets, retrieve metadata, track project history, and analyze geospatial data from your AI agent.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Upstream Lens on Vinkius

Get Property Details

Fetches specific, detailed records for a known property feature ID.

Get Organization Info

Retrieves core metadata about your entire organization within Upstream Lens.

Check Api Health

Confirms if the Upstream Lens API is currently active and connected.

List Property Imagery

Lists available satellite image layers (Sentinel, Landsat) for a specific property...

List Project Notes

Retrieves written field observations and notes, allowing filtering by update date...

List Project Observations

Lists detailed records of specific observations made during the course of a project.

List Portfolios

Lists all the high-level conservation portfolios you manage.

List Projects

Gathers a list of every active environmental project ID and name.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The Upstream Lens integration is available immediately — no restart needed.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Upstream Lens, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,100+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week
Upstream Lens MCP server cover

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Upstream Lens. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Sifting Through Environmental Reports takes Too Many Clicks Today.

Right now, tracking environmental data means jumping between a GIS portal for imagery, an internal database for property metadata, and a separate document management system for field notes. You spend half your day just copying IDs and pasting links into an email to assemble the full picture.

With this MCP server, you tell your agent exactly what you need—'Show me all assets in portfolio XYZ.' The agent handles the sequencing: it runs `list_projects`, grabs images with `list_property_imagery`, and pulls notes via `list_project_notes`. You get a single, synthesized answer.

Upstream Lens MCP Server: Get Structured Geospatial Data in Chat.

Before this, pulling data meant running manual reports and waiting hours for IT to stitch together the findings. If you needed a list of all assets, you'd run one report; if you needed imagery, you'd run another. Everything was siloed.

Now, asking 'What projects are active in the Midwest?' returns an immediate answer that combines project lists (`list_projects`), portfolio oversight (`list_portfolios`), and even confirms API connectivity status—all from the chat window.

What your AI can actually do with this

This server hooks your AI client up to Upstream Lens. You can run complex geospatial queries using plain language, pulling environmental data—like satellite images and field reports—and making it actionable right in the chat window.

Getting Started & Scope:
To make sure everything's running clean, you first need to check the connection status with check_api_health. For background info on your account, run get_organization_info; that pulls core metadata for your entire organization within Upstream Lens. You can scope out all the conservation work you manage by calling list_portfolios, which shows every high-level portfolio.

If you need to know what projects are active right now, list_projects gives you a list of every environmental project ID and name.

Property Deep Dive:
When you zero in on a specific piece of land, the server lets you pull down detailed records using get_property_details, which takes a known property feature ID to fetch all its specifics. For that same property, you can check what satellite images are available by calling list_property_imagery; this tool lists all layers—like Sentinel and Landsat—so you know if you're looking at true color or NDVI data.

If you just want the basics on a specific asset, you can also pull up comprehensive metadata about it using get_property_details.

Tracking Changes & History:
Environmental monitoring is all about tracking time. You don't have to leave the chat window to build an auditable timeline of site changes. If you need written field notes—the stuff people actually wrote down when they were out there—use list_project_notes. This lets you filter those observations by date for a specific project, so you can see exactly what was documented and when.

To get the granular details on what folks saw, use list_project_observations; this lists detailed records of every observation tied to a project. You can comb through all the historical documentation by targeting these tools against any given project ID.

Putting It All Together:
When you combine these calls, your AI client acts like it's sitting at the site with you. If you tell it, 'Show me all active projects and what imagery is available for the property associated with Project XYZ,' it pulls together a complete picture. You can see every portfolio (list_portfolios), confirm the API is live (check_api_health), get the project list (list_projects), pull down the latest satellite metadata (list_property_imagery)—and then, if you want to dig into the history of that spot, it pulls both the general notes (list_project_notes) and the specific observation records (list_project_observations).

It keeps your conservation data structured, verifiable, and immediately ready for whatever question you've got. You don't just get a list; you get the actionable context you need to make decisions.

Built · Hosted · Managed by Vinkius Upstream Lens MCP Server - Geospatial Monitoring Tool
Server ID 019dd17e-5f1e-7390-9622-b30a4b1eb624
Vinkius Inspector
Compliance Grade A+
Score 100/100
Vinkius Inspector Badge — Score 100/100

Questions you might have

How do I find all my environmental projects using list_projects? +

Just ask your agent to 'List all active environmental projects.' The list_projects tool runs immediately and gives you a clean, actionable roster of every project ID available in the system.

Can I check if the API is working before running any report? +

Yes. Run check_api_health. This simple call tells your agent instantly if the Upstream Lens connection is live, saving you from running expensive queries against a downed service.

Which tool do I use to find available satellite imagery? +

Use list_property_imagery and provide a specific property ID. This call tells you exactly which layers (Sentinel, Landsat) are available for that piece of land.

What's the difference between list_project_notes and list_project_observations? +

Project notes (list_project_notes) hold general text summaries written by field staff. Observations (list_project_observations) are typically structured, quantitative data points or metrics recorded at a specific time.

What does the `get_organization_info` tool retrieve about my Upstream Tech Lens account? +

The tool fetches core metadata for your entire organization. This helps confirm account configuration and verify basic credentials before you run larger, resource-intensive reports.

When should I use `get_property_details` instead of listing projects? +

Use this when you need the full metadata record for one specific feature. It retrieves deep details about a property—far beyond what general listings provide.

Can I use `list_project_notes` to filter observations by date range? +

Yes, you can specify an update date range when calling the tool. This lets you focus only on notes written between two specific dates for targeted analysis.

How does `list_portfolios` help manage my environmental assets? +

Portfolios group related projects and sites into a single container. Running this tool shows the high-level organizational structure of your conservation work.

Can I see if new satellite images are available for my project? +

Yes! Use the list_property_imagery tool and provide the Property ID. Your agent will retrieve all available imagery layers (Sentinel, Landsat, etc.) with their respective capture dates.

How do I retrieve field notes for a specific conservation project? +

Run the list_project_notes query with your Project ID. You can also provide an optional timestamp to filter only notes updated after a specific date.

Is it possible to see the geospatial metadata for a property feature? +

Absolutely. Use the get_property_details tool with the Feature ID to retrieve detailed geospatial data and metadata for any monitored property.

Built & Managed by Vinkius 30s setup 8 tools

We've already built the connector for Upstream Lens. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.